Item put and take detection using image recognition

ABSTRACT

Systems and techniques are provided for tracking puts and takes of inventory items by subjects in an area of real space. A plurality of cameras with overlapping fields of view produce respective sequences of images of corresponding fields of view in the real space. A processing system is coupled to the system. In one embodiment, the processing system comprises image recognition engines receiving corresponding sequences of images from the plurality of cameras. The image recognition engines process the images in the corresponding sequences to identify subjects represented in the images and generate classifications of the identified subjects. The system processes the classifications of identified subjects for sets of images in the sequences of images to detect takes and puts of inventory items on shelves by identified subjects.

PRIORITY APPLICATION

This application is a continuation-in-part of U.S. patent application Ser. No. 15/847,796 filed 19 Dec. 2017 (now U.S. Pat. No. 10,055,853); and benefit is claimed of U.S. Provisional Patent Application No. 62/542,077 filed 7 Aug. 2017. Both applications are incorporated herein by reference.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains material that is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.

REFERENCE TO COMPUTER PROGRAM LISTING APPENDIX

A computer program listing appendix (Copyright, Standard Cognition, Inc.) submitted electronically via the EFS-Web in ASCII text accompanies this application and is incorporated by reference. The name of the ASCII text file is “STCG_Computer_Program_Appx” created on 10 Jan. 2018 and is 21,742 bytes.

BACKGROUND Field

The present invention relates to systems that identify and track puts and takes of items by subjects in real space.

Description of Related Art

A difficult problem in image processing arises when images from multiple cameras disposed over large spaces are used to identify and track actions of subjects.

Tracking actions of subjects within an area of real space, such as a shopping store, present many technical challenges. For example, consider such an image processing system deployed in a shopping store with multiple customers moving in aisles between the shelves and open spaces within the shopping store. Customers take items from shelves and put those in their respective shopping carts or baskets. Customers may also put items on the shelf, if they do not want the item. While the customers are performing these actions, different portions of customers will be occluded in images from different cameras because of the presence of other customers, shelves, and product displays, etc. Also, there can be many customers in the store at any given time, making it difficult to identify and track individuals and their actions over time.

It is desirable to provide a system that can more effectively and automatically identify and track put and take actions of subjects in large spaces.

SUMMARY

A system, and method for operating a system, are provided for tracking puts and takes of inventory items by subjects, such as persons, in an area of real space using image processing. This function of tracking puts and takes by image processing presents a complex problem of computer engineering, relating to the type of image data to be processed, what processing of the image data to perform, and how to determine actions from the image data with high reliability. The system described herein can perform these functions using only images from cameras disposed overhead in the real space, so that no retrofitting of store shelves and floor space with sensors and the like is required for deployment in a given setting.

In an embodiment described herein, the system uses a plurality of cameras to produce respective sequences of images of corresponding fields of view in the real space. The field of view of each camera overlaps with the field of view of at least one other camera in the plurality of cameras. The system processes images in the sequences of images received from the plurality of cameras to identify subjects represented in the images and generate classifications of the identified subjects. Finally, the system processes the classifications of identified subjects for sets of images in the sequences of images to detect takes of inventory items by identified subjects and puts of inventory items on shelves by identified subjects.

In one embodiment, the classification identifies whether the identified subject is holding an inventory item. The classification also identifies whether a hand of the identified subject is near a shelf or whether a hand of the identified subject is near the identified subject. The classification of whether the hand is near the identified subject can include whether a hand of the identified subject is near to a basket associated with an identified subject, and near to the body of the identified subject.

Technology is described by which images representing a hand of a subject in the field of view can be processed to generate classifications of the hand of the subject in a plurality of images in time sequence. The classifications of the hand from a sequence of images can be processed, using a convolutional neural network in some embodiments, to identify an action by the subject. The actions can be put and takes of inventory items as set out in embodiments described herein, or other types of actions decipherable by processing images of hands.

Technology is described by which images are processed to identify subjects in the field of view, and to locate joints of the subjects. The location of joints of the subjects can be processed as described herein to identify bounding boxes in corresponding images that include the hands of the subjects. The data within the bounding boxes can be processed classifications of the hand of the subject in the corresponding image. The classifications of the hand from an identified subject generated in this way from a sequence of images can be processed to identify an action by the subject.

In one embodiment, the system includes circular buffers coupled to cameras in the plurality of cameras to store sets of images in the sequences of images from the plurality of cameras.

In one embodiment, the image recognition engines in the plurality of image recognition engines comprise convolutional neural networks.

In one embodiment, cameras in the plurality of cameras are configured to generate synchronized sequences of images.

In one embodiment, the plurality of cameras comprise cameras disposed over and having fields of view encompassing respective parts of the area in real space.

In one embodiment, the system includes logic to generate a log data structure (also referred to as shopping cart data structure) including a list of inventory items for each identified subject.

Tracking of puts and takes in real space by subjects presents a complex engineering problem. Technology is described here that processes sequences of images from multiple cameras, and in some embodiments using only the sequences of images, using a combination of image classification with time sequence analysis of the classifications of the images. The processes are implemented in embodiments described here using multiple trained neural networks.

The image classification as described here can be further divided into first processing the images from multiple cameras with overlapping fields of view to identify subjects, and second processing bounding boxes of data including hands of the subjects in the images from multiple cameras with overlapping fields of view to classify the conditions of the hands of the subjects, as the conditions relate to puts and takes. The time sequence analysis can be applied to the classifications of the conditions of the hands to produce with high confidence a record of the puts and takes of inventory items as the subject traverses a store.

Other aspects and advantages of the present invention can be seen on review of the drawings, the detailed description and the claims, which follow.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an architectural level schematic of a system in which a tracking engine tracks subjects using joint data generated by image recognition engines.

FIG. 2 is a side view of an aisle in a shopping store illustrating a camera arrangement.

FIG. 3 is a top view of the aisle of FIG. 2 in a shopping store illustrating a camera arrangement.

FIG. 4 is a camera and computer hardware arrangement configured for hosting an image recognition engine of FIG. 1.

FIG. 5 illustrates a convolutional neural network illustrating identification of joints in an image recognition engine of FIG. 1.

FIG. 6 shows an example data structure for storing joint information.

FIG. 7 illustrates the tracking engine of FIG. 1 with a global metric calculator.

FIG. 8 shows an example data structure for storing a subject including the information of associated joints.

FIG. 9 is a flowchart illustrating process steps for tracking subjects by the system of FIG. 1.

FIG. 10 is a flowchart showing more detailed process steps for a camera calibration step of FIG. 9.

FIG. 11 is a flowchart showing more detailed process steps for a video process step of FIG. 9.

FIG. 12A is a flowchart showing a first part of more detailed process steps for the scene process of FIG. 9.

FIG. 12B is a flowchart showing a second part of more detailed process steps for the scene process of FIG. 9.

FIG. 13 is an illustration of an environment in which an embodiment of the system of FIG. 1 is used.

FIG. 14 is an illustration of video and scene processes in an embodiment of the system of FIG. 1.

FIG. 15a is a schematic showing a pipeline with multiple convolutional neural networks (CNNs) including joints-CNN, WhatCNN and WhenCNN to generate a shopping cart data structure per subject in the real space.

FIG. 15b shows multiple image channels from multiple cameras and coordination logic for the subjects and their respective shopping cart data structures.

FIG. 16 is a flowchart illustrating process steps for identifying and updating subjects in the real space.

FIG. 17 is a flowchart showing process steps for processing hand joints of subjects to identify inventory items.

FIG. 18 is a flowchart showing process steps for time series analysis of inventory items per hand joint to create a shopping cart data structure per subject.

FIG. 19 is an illustration of a WhatCNN model in an embodiment of the system of FIG. 15 a.

FIG. 20 is an illustration of a WhenCNN model in an embodiment of the system of FIG. 15 a.

FIG. 21 presents an example architecture of a WhatCNN model identifying the dimensionality of convolutional layers.

FIG. 22 presents a high level block diagram of an embodiment of a WhatCNN model for classification of hand images.

FIG. 23 presents details of a first block of the high level block diagram of a WhatCNN model presented in FIG. 22.

FIG. 24 presents operators in a fully connected layer in the example WhatCNN model presented in FIG. 22.

FIG. 25 is an example name of an image file stored as part of the training data set for a WhatCNN model.

DETAILED DESCRIPTION

The following description is presented to enable any person skilled in the art to make and use the invention, and is provided in the context of a particular application and its requirements. Various modifications to the disclosed embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments and applications without departing from the spirit and scope of the present invention. Thus, the present invention is not intended to be limited to the embodiments shown but is to be accorded the widest scope consistent with the principles and features disclosed herein.

System Overview

A system and various implementations for tracking subjects are described with reference to FIGS. 1-16. The system and processes are described with reference to FIG. 1, an architectural level schematic of a system in accordance with an implementation. Because FIG. 1 is an architectural diagram, certain details are omitted to improve the clarity of the description.

The discussion of FIG. 1 is organized as follows. First, the elements of the system are described, followed by their interconnections. Then, the use of the elements in the system is described in greater detail.

FIG. 1 provides a block diagram level illustration of a system 100. The system 100 includes cameras 114, network nodes hosting image recognition engines 112 a, 112 b, and 112 n, a tracking engine 110 deployed in a network node (or nodes) on the network, a calibrator 120, a subject database 140, a training database 150, a joints heuristics database 160, a calibration database 170, and a communication network or networks 181.

As used herein, a network node is an addressable hardware device or virtual device that is attached to a network, and is capable of sending, receiving, or forwarding information over a communications channel to or from other network nodes. Examples of electronic devices which can be deployed as hardware network nodes include all varieties of computers, workstations, laptop computers, handheld computers, and smartphones. Network nodes can be implemented in a cloud-based server system. More than one virtual device configured as a network node can be implemented using a single physical device.

For the sake of clarity, only three network nodes hosting image recognition engines are shown in the system 100. However, any number of network nodes hosting image recognition engines can be connected to the tracking engine 110 through the network(s) 181. Also, an image recognition engine, a tracking engine and other processing engines described herein can execute using more than one network node in a distributed architecture.

The interconnection of the elements of system 100 will now be described. Network(s) 181 couples the network nodes 101 a, 101 b, and 101 c, respectively, hosting image recognition engines 112 a, 112 b, and 112 n, the network node 102 hosting the tracking engine 110, the calibrator 120, the subject database 140, the training database 150, the joints heuristics database 160, and the calibration database 170. Cameras 114 are connected to the tracking engine 110 through network nodes hosting image recognition engines 112 a, 112 b, and 112 n. In one embodiment, the cameras 114 are installed in a shopping store (such as a supermarket) such that sets of cameras 114 (two or more) with overlapping fields of view are positioned over each aisle to capture images of real space in the store. In FIG. 1, two cameras are arranged over aisle 116 a, two cameras are arranged over aisle 116 b, and three cameras are arranged over aisle 116 n. The cameras 114 are installed over aisles with overlapping fields of view. In such an embodiment, the cameras are configured with the goal that customers moving in the aisles of the shopping store are present in the field of view of two or more cameras at any moment in time.

Cameras 114 can be synchronized in time with each other, so that images are captured at the same time, or close in time, and at the same image capture rate. The cameras 114 can send respective continuous streams of images at a predetermined rate to network nodes hosting image recognition engines 112 a-112 n. Images captured in all the cameras covering an area of real space at the same time, or close in time, are synchronized in the sense that the synchronized images can be identified in the processing engines as representing different views of subjects having fixed positions in the real space. For example, in one embodiment, the cameras send image frames at the rates of 30 frames per second (fps) to respective network nodes hosting image recognition engines 112 a-112 n. Each frame has a timestamp, identity of the camera (abbreviated as “camera_id”), and a frame identity (abbreviated as “frame_id”) along with the image data.

Cameras installed over an aisle are connected to respective image recognition engines. For example, in FIG. 1, the two cameras installed over the aisle 116 a are connected to the network node 101 a hosting an image recognition engine 112 a. Likewise, the two cameras installed over aisle 116 b are connected to the network node 101 b hosting an image recognition engine 112 b. Each image recognition engine 112 a-112 n hosted in a network node or nodes 101 a-101 n, separately processes the image frames received from one camera each in the illustrated example.

In one embodiment, each image recognition engine 112 a, 112 b, and 112 n is implemented as a deep learning algorithm such as a convolutional neural network (abbreviated CNN). In such an embodiment, the CNN is trained using a training database 150. In an embodiment described herein, image recognition of subjects in the real space is based on identifying and grouping joints recognizable in the images, where the groups of joints can be attributed to an individual subject. For this joints based analysis, the training database 150 has a large collection of images for each of the different types of joints for subjects. In the example embodiment of a shopping store, the subjects are the customers moving in the aisles between the shelves. In an example embodiment, during training of the CNN, the system 100 is referred to as a “training system”. After training the CNN using the training database 150, the CNN is switched to production mode to process images of customers in the shopping store in real time. In an example embodiment, during production, the system 100 is referred to as a runtime system (also referred to as an inference system). The CNN in each image recognition engine produces arrays of joints data structures for images in its respective stream of images. In an embodiment as described herein, an array of joints data structures is produced for each processed image, so that each image recognition engine 112 a-112 n produces an output stream of arrays of joints data structures. These arrays of joints data structures from cameras having overlapping fields of view are further processed to form groups of joints, and to identify such groups of joints as subjects.

The cameras 114 are calibrated before switching the CNN to production mode. The calibrator 120 calibrates the cameras and stores the calibration data in the calibration database 170.

The tracking engine 110, hosted on the network node 102, receives continuous streams of arrays of joints data structures for the subjects from image recognition engines 112 a-112 n. The tracking engine 110 processes the arrays of joints data structures and translates the coordinates of the elements in the arrays of joints data structures corresponding to images in different sequences into candidate joints having coordinates in the real space. For each set of synchronized images, the combination of candidate joints identified throughout the real space can be considered, for the purposes of analogy, to be like a galaxy of candidate joints. For each succeeding point in time, movement of the candidate joints is recorded so that the galaxy changes over time. The output of the tracking engine 110 is stored in the subject database 140.

The tracking engine 110 uses logic to identify groups or sets of candidate joints having coordinates in real space as subjects in the real space. For the purposes of analogy, each set of candidate points is like a constellation of candidate joints at each point in time. The constellations of candidate joints can move over time.

The logic to identify sets of candidate joints comprises heuristic functions based on physical relationships amongst joints of subjects in real space. These heuristic functions are used to identify sets of candidate joints as subjects. The heuristic functions are stored in joints heuristics database 160. The output of the tracking engine 110 is stored in the subject database 140. Thus, the sets of candidate joints comprise individual candidate joints that have relationships according to the heuristic parameters with other individual candidate joints and subsets of candidate joints in a given set that has been identified, or can be identified, as an individual subject.

The actual communication path through the network 181 can be point-to-point over public and/or private networks. The communications can occur over a variety of networks 181, e.g., private networks, VPN, MPLS circuit, or Internet, and can use appropriate application programming interfaces (APIs) and data interchange formats, e.g., Representational State Transfer (REST), JavaScript Object Notation (JSON), Extensible Markup Language (XML), Simple Object Access Protocol (SOAP), Java™ Message Service (JMS), and/or Java Platform Module System. All of the communications can be encrypted. The communication is generally over a network such as a LAN (local area network), WAN (wide area network), telephone network (Public Switched Telephone Network (PSTN), Session Initiation Protocol (SIP), wireless network, point-to-point network, star network, token ring network, hub network, Internet, inclusive of the mobile Internet, via protocols such as EDGE, 3G, 4G LTE, Wi-Fi, and WiMAX. Additionally, a variety of authorization and authentication techniques, such as username/password, Open Authorization (OAuth), Kerberos, SecureID, digital certificates and more, can be used to secure the communications.

The technology disclosed herein can be implemented in the context of any computer-implemented system including a database system, a multi-tenant environment, or a relational database implementation like an Oracle™ compatible database implementation, an IBM DB2 Enterprise Server™ compatible relational database implementation, a MySQL™ or PostgreSQL™ compatible relational database implementation or a Microsoft SQL Server™ compatible relational database implementation or a NoSQL™ non-relational database implementation such as a Vampire™ compatible non-relational database implementation, an Apache Cassandra™ compatible non-relational database implementation, a BigTable™ compatible non-relational database implementation or an HBase™ or DynamoDB™ compatible non-relational database implementation. In addition, the technology disclosed can be implemented using different programming models like MapReduce™, bulk synchronous programming, MPI primitives, etc. or different scalable batch and stream management systems like Apache Storm™, Apache Spark™, Apache Kafka™, Apache Flink™ Truviso™, Amazon Elasticsearch Service™, Amazon Web Services™ (AWS), IBM Info-Sphere™, Borealis™, and Yahoo! S4™.

Camera Arrangement

The cameras 114 are arranged to track multi-joint entities in a three-dimensional (abbreviated as 3D) real space. In the example embodiment of the shopping store, the real space can include the area of the shopping store where items for sale are stacked in shelves. A point in the real space can be represented by an (x, y, z) coordinate system. Each point in the area of real space for which the system is deployed is covered by the fields of view of two or more cameras 114.

In a shopping store, the shelves can be arranged in a variety of manners, such as along the walls of the shopping store, or in rows forming aisles or a combination of the two arrangements. FIG. 2 shows an arrangement of shelves, forming an aisle 116 a, viewed from one end of the aisle 116 a. Two cameras, camera A 206 and camera B 208 are positioned over the aisle 116 a at a predetermined distance from a roof 230 and a floor 220 of the shopping store. The cameras 114 comprise cameras disposed over and having fields of view encompassing respective parts of the floor area in the real space, and the coordinates in real space of members of a set of candidate joints, identified as a subject, identify locations in the floor area of the subject. In the example embodiment of the shopping store, the real space can include all of the floor 220 in the shopping store from which inventory can be accessed. Cameras 114 are placed and oriented such that areas of the floor 220 and shelves can be seen by at least two cameras. The cameras 114 also cover floor space in front of the shelves 202 and 204. Camera angles are selected to have both steep perspective, straight down, and angled perspectives that give more full body images of the customers. In one example embodiment, the cameras 114 are configured at an eight (8) foot height or higher throughout the shopping store. FIG. 13 presents an illustration of such an embodiment.

In FIG. 2, the cameras 206 and 208 have overlapping fields of view, covering the space between a shelf A 202 and a shelf B 204 with overlapping fields of view 216 and 218, respectively. A location in the real space is represented as a (x, y, z) point of the real space coordinate system. “x” and “y” represent positions on a two-dimensional (2D) plane which can be the floor 220 of the shopping store. The value “z” is the height of the point above the 2D plane at floor 220 in one configuration.

FIG. 3 illustrates the aisle 116 a viewed from the top of FIG. 2, further showing an example arrangement of the positions of cameras 206 and 208 over the aisle 116 a. The cameras 206 and 208 are positioned closer to opposite ends of the aisle 116 a. The camera A 206 is positioned at a predetermined distance from the shelf A 202 and the camera B 208 is positioned at a predetermined distance from the shelf B 204. In another embodiment, in which more than two cameras are positioned over an aisle, the cameras are positioned at equal distances from each other. In such an embodiment, two cameras are positioned close to the opposite ends and a third camera is positioned in the middle of the aisle. It is understood that a number of different camera arrangements are possible.

Camera Calibration

The camera calibrator 120 performs two types of calibrations: internal and external. In internal calibration, the internal parameters of the cameras 114 are calibrated. Examples of internal camera parameters include focal length, principal point, skew, fisheye coefficients, etc. A variety of techniques for internal camera calibration can be used. One such technique is presented by Zhang in “A flexible new technique for camera calibration” published in IEEE Transactions on Pattern Analysis and Machine Intelligence, Volume 22, No. 11, November 2000.

In external calibration, the external camera parameters are calibrated in order to generate mapping parameters for translating the 2D image data into 3D coordinates in real space. In one embodiment, one subject, such as a person, is introduced into the real space. The subject moves through the real space on a path that passes through the field of view of each of the cameras 114. At any given point in the real space, the subject is present in the fields of view of at least two cameras forming a 3D scene. The two cameras, however, have a different view of the same 3D scene in their respective two-dimensional (2D) image planes. A feature in the 3D scene such as a left-wrist of the subject is viewed by two cameras at different positions in their respective 2D image planes.

A point correspondence is established between every pair of cameras with overlapping fields of view for a given scene. Since each camera has a different view of the same 3D scene, a point correspondence is two pixel locations (one location from each camera with overlapping field of view) that represent the projection of the same point in the 3D scene. Many point correspondences are identified for each 3D scene using the results of the image recognition engines 112 a-112 n for the purposes of the external calibration. The image recognition engines identify the position of a joint as (x, y) coordinates, such as row and column numbers, of pixels in the 2D image planes of respective cameras 114. In one embodiment, a joint is one of 19 different types of joints of the subject. As the subject moves through the fields of view of different cameras, the tracking engine 110 receives (x, y) coordinates of each of the 19 different types of joints of the subject used for the calibration from cameras 114 per image.

For example, consider an image from a camera A and an image from a camera B both taken at the same moment in time and with overlapping fields of view. There are pixels in an image from camera A that correspond to pixels in a synchronized image from camera B. Consider that there is a specific point of some object or surface in view of both camera A and camera B and that point is captured in a pixel of both image frames. In external camera calibration, a multitude of such points are identified and referred to as corresponding points. Since there is one subject in the field of view of camera A and camera B during calibration, key joints of this subject are identified, for example, the center of left wrist. If these key joints are visible in image frames from both camera A and camera B then it is assumed that these represent corresponding points. This process is repeated for many image frames to build up a large collection of corresponding points for all pairs of cameras with overlapping fields of view. In one embodiment, images are streamed off of all cameras at a rate of 30 FPS (frames per second) or more and a resolution of 720 pixels in full RGB (red, green, and blue) color. These images are in the form of one-dimensional arrays (also referred to as flat arrays).

The large number of images collected above for a subject can be used to determine corresponding points between cameras with overlapping fields of view. Consider two cameras A and B with overlapping field of view. The plane passing through camera centers of cameras A and B and the joint location (also referred to as feature point) in the 3D scene is called the “epipolar plane”. The intersection of the epipolar plane with the 2D image planes of the cameras A and B defines the “epipolar line”. Given these corresponding points, a transformation is determined that can accurately map a corresponding point from camera A to an epipolar line in camera B's field of view that is guaranteed to intersect the corresponding point in the image frame of camera B. Using the image frames collected above for a subject, the transformation is generated. It is known in the art that this transformation is non-linear. The general form is furthermore known to require compensation for the radial distortion of each camera's lens, as well as the non-linear coordinate transformation moving to and from the projected space. In external camera calibration, an approximation to the ideal non-linear transformation is determined by solving a non-linear optimization problem. This non-linear optimization function is used by the tracking engine 110 to identify the same joints in outputs (arrays of joints data structures) of different image recognition engines 112 a-112 n, processing images of cameras 114 with overlapping fields of view. The results of the internal and external camera calibration are stored in the calibration database 170.

A variety of techniques for determining the relative positions of the points in images of cameras 114 in the real space can be used. For example, Longuet-Higgins published, “A computer algorithm for reconstructing a scene from two projections” in Nature, Volume 293, 10 Sep. 1981. This paper presents computing a three-dimensional structure of a scene from a correlated pair of perspective projections when spatial relationship between the two projections is unknown. The Longuet-Higgins paper presents a technique to determine the position of each camera in the real space with respect to other cameras. Additionally, their technique allows triangulation of a subject in the real space, identifying the value of the z-coordinate (height from the floor) using images from cameras 114 with overlapping fields of view. An arbitrary point in the real space, for example, the end of a shelf in one corner of the real space, is designated as a (0, 0, 0) point on the (x, y, z) coordinate system of the real space.

In an embodiment of the technology, the parameters of the external calibration are stored in two data structures. The first data structure stores intrinsic parameters. The intrinsic parameters represent a projective transformation from the 3D coordinates into 2D image coordinates. The first data structure contains intrinsic parameters per camera as shown below. The data values are all numeric floating point numbers. This data structure stores a 3×3 intrinsic matrix, represented as “K” and distortion coefficients. The distortion coefficients include six radial distortion coefficients and two tangential distortion coefficients. Radial distortion occurs when light rays bend more near the edges of a lens than they do at its optical center. Tangential distortion occurs when the lens and the image plane are not parallel. The following data structure shows values for the first camera only. Similar data is stored for all the cameras 114.

-   {     -   1:{         -   K: [[x, x, x], [x, x, x], [x, x, x]],         -   distortion coefficients: [x, x, x, x, x, x, x, x]     -   },     -   . . . -   }

The second data structure stores per pair of cameras: a 3×3 fundamental matrix (F), a 3×3 essential matrix (E), a 3×4 projection matrix (P), a 3×3 rotation matrix (R) and a 3×1 translation vector (t). This data is used to convert points in one camera's reference frame to another camera's reference frame. For each pair of cameras, eight homography coefficients are also stored to map the plane of the floor 220 from one camera to another. A fundamental matrix is a relationship between two images of the same scene that constrains where the projection of points from the scene can occur in both images. Essential matrix is also a relationship between two images of the same scene with the condition that the cameras are calibrated. The projection matrix gives a vector space projection from 3D real space to a subspace. The rotation matrix is used to perform a rotation in Euclidean space. Translation vector “t” represents a geometric transformation that moves every point of a figure or a space by the same distance in a given direction. The homography_floor_coefficients are used to combine images of features of subjects on the floor 220 viewed by cameras with overlapping fields of views. The second data structure is shown below. Similar data is stored for all pairs of cameras. As indicated previously, the x's represents numeric floating point numbers.

-   {     -   1: {         -   2: {             -   F: [[x, x, x], [x, x, x], [x, x, x]],             -   E: [[x, x, x], [x, x, x], [x, x, x]],             -   P: [[x, x, x, x], [x, x, x, x], [x, x, x, x]],             -   R: [[x, x, x], [x, x, x], [x, x, x]],             -   t: [x, x, x],             -   homography floor coefficients: [x, x, x, x, x, x, x, x]         -   }     -   }     -   . . . -   }     Network Configuration

FIG. 4 presents an architecture 400 of a network hosting image recognition engines. The system includes a plurality of network nodes 101 a-101 n in the illustrated embodiment. In such an embodiment, the network nodes are also referred to as processing platforms. Processing platforms 101 a-101 n and cameras 412, 414, 416, . . . 418 are connected to network(s) 481.

FIG. 4 shows a plurality of cameras 412, 414, 416, . . . 418 connected to the network(s). A large number of cameras can be deployed in particular systems. In one embodiment, the cameras 412 to 418 are connected to the network(s) 481 using Ethernet-based connectors 422, 424, 426, and 428, respectively. In such an embodiment, the Ethernet-based connectors have a data transfer speed of 1 gigabit per second, also referred to as Gigabit Ethernet. It is understood that in other embodiments, cameras 114 are connected to the network using other types of network connections which can have a faster or slower data transfer rate than Gigabit Ethernet. Also, in alternative embodiments, a set of cameras can be connected directly to each processing platform, and the processing platforms can be coupled to a network.

Storage subsystem 430 stores the basic programming and data constructs that provide the functionality of certain embodiments of the present invention. For example, the various modules implementing the functionality of image recognition engines of the invention may be stored in storage subsystem 430. The storage subsystem 430 is an example of a computer readable memory comprising a non-transitory data storage medium, having computer instructions stored in the memory executable by a computer to track subjects in an area of real space by processes as described herein. In other examples, the computer instructions can be stored in other types of memory, including portable memory, that comprise a non-transitory data storage medium or media, readable by a computer.

These software modules are generally executed by a processor subsystem 450. A host memory subsystem 432 typically includes a number of memories including a main random access memory (RAM) 434 for storage of instructions and data during program execution and a read-only memory (ROM) 436 in which fixed instructions are stored. In one embodiment, the RAM 434 is used as a buffer for storing video streams from the cameras 114 connected to the platform 101 a.

A file storage subsystem 440 provides persistent storage for program and data files. In an example embodiment, the storage subsystem 440 includes four 120 Gigabyte (GB) solid state disks (SSD) in a RAID 0 (redundant array of independent disks) arrangement identified by a numeral 442. In the example embodiment, in which CNN is used to identify joints of subjects, the RAID 0 442 is used to store training data. During training, the training data which is not in RAM 434 is read from RAID 0 442. Similarly, when images are being recorded for training purposes, the data which is not in RAM 434 is stored in RAID 0 442. In the example embodiment, the hard disk drive (HDD) 446 is a 10 terabyte storage. It is slower in access speed than the RAID 0 442 storage. The solid state disk (SSD) 444 contains the operating system and related files for the image recognition engine 112 a.

In an example configuration, three cameras 412, 414, and 416, are connected to the processing platform 101 a. Each camera has a dedicated graphics processing unit GPU 1 462, GPU 2 464, and GPU 3 466, to process images sent by the camera. It is understood that fewer than or more than three cameras can be connected per processing platform. Accordingly, fewer or more GPUs are configured in the network node so that each camera has a dedicated GPU for processing the image frames received from the camera. The processor subsystem 450, the storage subsystem 430 and the GPUs 462, 464, and 466 communicate using the bus subsystem 454.

A number of peripheral devices such as a network interface subsystem, user interface output devices, and user interface input devices are also connected to the bus subsystem 454 forming part of the processing platform 101 a. These subsystems and devices are intentionally not shown in FIG. 4 to improve the clarity of the description. Although bus subsystem 454 is shown schematically as a single bus, alternative embodiments of the bus subsystem may use multiple busses.

In one embodiment, the cameras 412 can be implemented using Chameleon3 1.3 MP Color USB3 Vision (Sony ICX445), having a resolution of 1288×964, a frame rate of 30 FPS, and at 1.3 MegaPixels per image, with Varifocal Lens having a working distance (mm) of 300-∞, a field of view field of view with a ⅓″ sensor of 98.2°-23.8°.

Convolutional Neural Network

The image recognition engines 112 a-112 n in the processing platforms 101 a-101 n receive a continuous stream of images at a predetermined rate. In one embodiment, the image recognition engines comprise convolutional neural networks (abbreviated CNN).

FIG. 5 illustrates processing of image frames by a CNN referred to by a numeral 500. The input image 510 is a matrix consisting of image pixels arranged in rows and columns. In one embodiment, the input image 510 has a width of 1280 pixels, height of 720 pixels and 3 channels red, blue, and green also referred to as RGB. The channels can be imagined as three 1280×720 two-dimensional images stacked over one another. Therefore, the input image has dimensions of 1280×720×3 as shown in FIG. 5.

A 2×2 filter 520 is convolved with the input image 510. In this embodiment, no padding is applied when the filter is convolved with the input. Following this, a nonlinearity function is applied to the convolved image. In the present embodiment, rectified linear unit (ReLU) activations are used. Other examples of nonlinear functions include sigmoid, hyperbolic tangent (tan h) and variations of ReLU such as leaky ReLU. A search is performed to find hyper-parameter values. The hyper-parameters are C₁, C₂, . . . , C_(N) where C_(N) means the number of channels for convolution layer “N”. Typical values of N and C are shown in FIG. 5. There are twenty five (25) layers in the CNN as represented by N equals 25. The values of C are the number of channels in each convolution layer for layers 1 to 25. In other embodiments, additional features are added to the CNN 500 such as residual connections, squeeze-excitation modules, and multiple resolutions.

In typical CNNs used for image classification, the size of the image (width and height dimensions) is reduced as the image is processed through convolution layers. That is helpful in feature identification as the goal is to predict a class for the input image. However, in the illustrated embodiment, the size of the input image (i.e. image width and height dimensions) is not reduced, as the goal is to not only to identify a joint (also referred to as a feature) in the image frame, but also to identify its exact location in the image so it can be mapped to coordinates in the real space. Therefore, as shown FIG. 5, the width and height dimensions of the image remain unchanged as the processing proceeds through convolution layers of the CNN.

In one embodiment, the CNN 500 identifies one of the 19 possible joints of the subjects at each element of the image. The possible joints can be grouped in two categories: foot joints and non-foot joints. The 19^(th) type of joint classification is for all non-joint features of the subject (i.e. elements of the image not classified as a joint).

Foot Joints:

-   -   Ankle joint (left and right)

Non-Foot Joints:

-   -   Neck     -   Nose     -   Eyes (left and right)     -   Ears (left and right)     -   Shoulders (left and right)     -   Elbows (left and right)     -   Wrists (left and right)     -   Hip (left and right)     -   Knees (left and right)

Not a Joint

As can be seen, a “joint” for the purposes of this description is a trackable feature of a subject in the real space. A joint may correspond to physiological joints on the subjects, or other features such as the eye, or nose.

The first set of analyses on the stream of input images identifies trackable features of subjects in real space. In one embodiment, this is referred to as “joints analysis”. In such an embodiment, the CNN used for joints analysis is referred to as “joints CNN”. In one embodiment, the joints analysis is performed thirty times per second over thirty frames per second received from the corresponding camera. The analysis is synchronized in time i.e., at 1/30^(th) of a second, images from all cameras 114 are analyzed in the corresponding joints CNNs to identify joints of all subjects in the real space. The results of this analysis of the images from a single moment in time from plural cameras is stored as a “snapshot”.

A snapshot can be in the form of a dictionary containing arrays of joints data structures from images of all cameras 114 at a moment in time, representing a constellation of candidate joints within the area of real space covered by the system. In one embodiment, the snapshot is stored in the subject database 140.

In this example CNN, a softmax function is applied to every element of the image in the final layer of convolution layers 530. The softmax function transforms a K-dimensional vector of arbitrary real values to a K-dimensional vector of real values in the range [0, 1] that add up to 1. In one embodiment, an element of an image is a single pixel. The softmax function converts the 19-dimensional array (also referred to a 19-dimensional vector) of arbitrary real values for each pixel to a 19-dimensional confidence array of real values in the range [0, 1] that add up to 1. The 19 dimensions of a pixel in the image frame correspond to the 19 channels in the final layer of the CNN which further correspond to 19 types of joints of the subjects.

A large number of picture elements can be classified as one of each of the 19 types of joints in one image depending on the number of subjects in the field of view of the source camera for that image.

The image recognition engines 112 a-112 n process images to generate confidence arrays for elements of the image. A confidence array for a particular element of an image includes confidence values for a plurality of joint types for the particular element. Each one of the image recognition engines 112 a-112 n, respectively, generates an output matrix 540 of confidence arrays per image. Finally, each image recognition engine generates arrays of joints data structures corresponding to each output matrix 540 of confidence arrays per image. The arrays of joints data structures corresponding to particular images classify elements of the particular images by joint type, time of the particular image, and coordinates of the element in the particular image. A joint type for the joints data structure of the particular elements in each image is selected based on the values of the confidence array.

Each joint of the subjects can be considered to be distributed in the output matrix 540 as a heat map. The heat map can be resolved to show image elements having the highest values (peak) for each joint type. Ideally, for a given picture element having high values of a particular joint type, surrounding picture elements outside a range from the given picture element will have lower values for that joint type, so that a location for a particular joint having that joint type can be identified in the image space coordinates. Correspondingly, the confidence array for that image element will have the highest confidence value for that joint and lower confidence values for the remaining 18 types of joints.

In one embodiment, batches of images from each camera 114 are processed by respective image recognition engines. For example, six contiguously timestamped images are processed sequentially in a batch to take advantage of cache coherence. The parameters for one layer of the CNN 500 are loaded in memory and applied to the batch of six image frames. Then the parameters for the next layer are loaded in memory and applied to the batch of six images. This is repeated for all convolution layers 530 in the CNN 500. The cache coherence reduces processing time and improves performance of the image recognition engines.

In one such embodiment, referred to as three dimensional (3D) convolution, a further improvement in performance of the CNN 500 is achieved by sharing information across image frames in the batch. This helps in more precise identification of joints and reduces false positives. For examples, features in the image frames for which pixel values do not change across the multiple image frames in a given batch are likely static objects such as a shelf. The change of values for the same pixel across image frames in a given batch indicates that this pixel is likely a joint. Therefore, the CNN 500 can focus more on processing that pixel to accurately identify the joint identified by that pixel.

Joints Data Structure

The output of the CNN 500 is a matrix of confidence arrays for each image per camera. The matrix of confidence arrays is transformed into an array of joints data structures. A joints data structure 600 as shown in FIG. 6 is used to store the information of each joint. The joints data structure 600 identifies x and y positions of the element in the particular image in the 2D image space of the camera from which the image is received. A joint number identifies the type of joint identified. For example, in one embodiment, the values range from 1 to 19. A value of 1 indicates that the joint is a left-ankle, a value of 2 indicates the joint is a right-ankle and so on. The type of joint is selected using the confidence array for that element in the output matrix 540. For example, in one embodiment, if the value corresponding to the left-ankle joint is highest in the confidence array for that image element, then the value of the joint number is “1”.

A confidence number indicates the degree of confidence of the CNN 500 in predicting that joint. If the value of confidence number is high, it means the CNN is confident in its prediction. An integer-Id is assigned to the joints data structure to uniquely identify it. Following the above mapping, the output matrix 540 of confidence arrays per image is converted into an array of joints data structures for each image.

The image recognition engines 112 a-112 n receive the sequences of images from cameras 114 and process images to generate corresponding arrays of joints data structures as described above. An array of joints data structures for a particular image classifies elements of the particular image by joint type, time of the particular image, and the coordinates of the elements in the particular image. In one embodiment, the image recognition engines 112 a-112 n are convolutional neural networks CNN 500, the joint type is one of the 19 types of joints of the subjects, the time of the particular image is the timestamp of the image generated by the source camera 114 for the particular image, and the coordinates (x, y) identify the position of the element on a 2D image plane.

In one embodiment, the joints analysis includes performing a combination of k-nearest neighbors, mixture of Gaussians, various image morphology transformations, and joints CNN on each input image. The result comprises arrays of joints data structures which can be stored in the form of a bit mask in a ring buffer that maps image numbers to bit masks at each moment in time.

Tracking Engine

The tracking engine 110 is configured to receive arrays of joints data structures generated by the image recognition engines 112 a-112 n corresponding to images in sequences of images from cameras having overlapping fields of view. The arrays of joints data structures per image are sent by image recognition engines 112 a-112 n to the tracking engine 110 via the network(s) 181 as shown in FIG. 7. The tracking engine 110 translates the coordinates of the elements in the arrays of joints data structures corresponding to images in different sequences into candidate joints having coordinates in the real space. The tracking engine 110 comprises logic to identify sets of candidate joints having coordinates in real space (constellations of joints) as subjects in the real space. In one embodiment, the tracking engine 110 accumulates arrays of joints data structures from the image recognition engines for all the cameras at a given moment in time and stores this information as a dictionary in the subject database 140, to be used for identifying a constellation of candidate joints. The dictionary can be arranged in the form of key-value pairs, where keys are camera ids and values are arrays of joints data structures from the camera. In such an embodiment, this dictionary is used in heuristics-based analysis to determine candidate joints and for assignment of joints to subjects. In such an embodiment, a high-level input, processing and output of the tracking engine 110 is illustrated in table 1.

TABLE 1 Inputs, processing and outputs from tracking engine 110 in an example embodiment. Inputs Processing Output Arrays of joints data Create joints dictionary List of subjects in structures per image Reproject joint positions thereal space at a and for each joints in the fields of view of moment in time data structure  Unique ID cameras with  Confidence number overlapping fields of  Joint number view to candidate joints  (x, y) position in  image space Grouping Joints into Candidate Joints

The tracking engine 110 receives arrays of joints data structures along two dimensions: time and space. Along the time dimension, the tracking engine receives sequentially timestamped arrays of joints data structures processed by image recognition engines 112 a-112 n per camera. The joints data structures include multiple instances of the same joint of the same subject over a period of time in images from cameras having overlapping fields of view. The (x, y) coordinates of the element in the particular image will usually be different in sequentially timestamped arrays of joints data structures because of the movement of the subject to which the particular joint belongs. For example, twenty picture elements classified as left-wrist joints can appear in many sequentially timestamped images from a particular camera, each left-wrist joint having a position in real space that can be changing or unchanging from image to image. As a result, twenty left-wrist joints data structures 600 in many sequentially timestamped arrays of joints data structures can represent the same twenty joints in real space over time.

Because multiple cameras having overlapping fields of view cover each location in the real space, at any given moment in time, the same joint can appear in images of more than one of the cameras 114. The cameras 114 are synchronized in time, therefore, the tracking engine 110 receives joints data structures for a particular joint from multiple cameras having overlapping fields of view, at any given moment in time. This is the space dimension, the second of the two dimensions: time and space, along which the tracking engine 110 receives data in arrays of joints data structures.

The tracking engine 110 uses an initial set of heuristics stored in the joints heuristics database 160 to identify candidate joints data structures from the arrays of joints data structures. The goal is to minimize a global metric over a period of time. A global metric calculator 702 calculates the global metric. The global metric is a summation of multiple values described below. Intuitively, the value of the global metric is minimum when the joints in arrays of joints data structures received by the tracking engine 110 along the time and space dimensions are correctly assigned to respective subjects. For example, consider the embodiment of the shopping store with customers moving in the aisles. If the left-wrist of a customer A is incorrectly assigned to a customer B, then the value of the global metric will increase. Therefore, minimizing the global metric for each joint for each customer is an optimization problem. One option to solve this problem is to try all possible connections of joints. However, this can become intractable as the number of customers increases.

A second approach to solve this problem is to use heuristics to reduce possible combinations of joints identified as members of a set of candidate joints for a single subject. For example, a left-wrist joint cannot belong to a subject far apart in space from other joints of the subject because of known physiological characteristics of the relative positions of joints. Similarly, a left-wrist joint having a small change in position from image to image is less likely to belong to a subject having the same joint at the same position from an image far apart in time, because the subjects are not expected to move at a very high speed. These initial heuristics are used to build boundaries in time and space for constellations of candidate joints that can be classified as a particular subject. The joints in the joints data structures within a particular time and space boundary are considered as “candidate joints” for assignment to sets of candidate joints as subjects present in the real space. These candidate joints include joints identified in arrays of joints data structures from multiple images from a same camera over a period of time (time dimension) and across different cameras with overlapping fields of view (space dimension).

Foot Joints

The joints can be divided for the purposes of a procedure for grouping the joints into constellations, into foot and non-foot joints as shown above in the list of joints. The left and right-ankle joint types in the current example, are considered foot joints for the purpose of this procedure. The tracking engine 110 can start identification of sets of candidate joints of particular subjects using foot joints. In the embodiment of the shopping store, the feet of the customers are on the floor 220 as shown in FIG. 2. The distance of the cameras 114 to the floor 220 is known. Therefore, when combining the joints data structures of foot joints from arrays of data joints data structures corresponding to images of cameras with overlapping fields of view, the tracking engine 110 can assume a known depth (distance along z axis). The value depth for foot joints is zero i.e. (x, y, 0) in the (x, y, z) coordinate system of the real space. Using this information, the image tracking engine 110 applies homographic mapping to combine joints data structures of foot joints from cameras with overlapping fields of view to identify the candidate foot joint. Using this mapping, the location of the joint in (x, y) coordinates in image space is converted to the location in the (x, y, z) coordinates in the real space, resulting in a candidate foot joint. This process is performed separately to identify candidate left and right foot joints using respective joints data structures.

Following this, the tracking engine 110 can combine a candidate left foot joint and a candidate right foot joint (assigns them to a set of candidate joints) to create a subject. Other joints from the galaxy of candidate joints can be linked to the subject to build a constellation of some or all of the joint types for the created subject.

If there is only one left candidate foot joint and one right candidate foot joint then it means there is only one subject in the particular space at the particular time. The tracking engine 110 creates a new subject having the left and the right candidate foot joints belonging to its set of joints. The subject is saved in the subject database 140. If there are multiple candidate left and right foot joints, then the global metric calculator 702 attempts to combine each candidate left foot joint to each candidate right foot joint to create subjects such that the value of the global metric is minimized.

Non-Foot Joints

To identify candidate non-foot joints from arrays of joints data structures within a particular time and space boundary, the tracking engine 110 uses the non-linear transformation (also referred to as a fundamental matrix) from any given camera A to its neighboring camera B with overlapping fields of view. The non-linear transformations are calculated using a single multi-joint subject and stored in the calibration database 170 as described above. For example, for two cameras A and B with overlapping fields of view, the candidate non-foot joints are identified as follows. The non-foot joints in arrays of joints data structures corresponding to elements in image frames from camera A are mapped to epipolar lines in synchronized image frames from camera B. A joint (also referred to as a feature in machine vision literature) identified by a joints data structure in an array of joints data structures of a particular image of camera A will appear on a corresponding epipolar line if it appears in the image of camera B. For example, if the joint in the joints data structure from camera A is a left-wrist joint, then a left-wrist joint on the epipolar line in the image of camera B represents the same left-wrist joint from the perspective of camera B. These two points in images of cameras A and B are projections of the same point in the 3D scene in real space and are referred to as a “conjugate pair”.

Machine vision techniques such as the technique by Longuet-Higgins published in the paper, titled, “A computer algorithm for reconstructing a scene from two projections” in Nature, Volume 293, 10 Sep. 1981, are applied to conjugate pairs of corresponding points to determine height of joints from the floor 220 in the real space. Application of the above method requires predetermined mapping between cameras with overlapping fields of view. That data is stored in the calibration database 170 as non-linear functions determined during the calibration of the cameras 114 described above.

The tracking engine 110 receives the arrays of joints data structures corresponding to images in sequences of images from cameras having overlapping fields of view, and translates the coordinates of the elements in the arrays of joints data structures corresponding to images in different sequences into candidate non-foot joints having coordinates in the real space. The identified candidate non-foot joints are grouped into sets of subjects having coordinates in real space using the global metric calculator 702. The global metric calculator 702 calculates the global metric value and attempts to minimize the value by checking different combinations of non-foot joints. In one embodiment, the global metric is a sum of heuristics organized in four categories. The logic to identify sets of candidate joints comprises heuristic functions based on physical relationships among joints of subjects in real space to identify sets of candidate joints as subjects. Examples of physical relationships among joints are considered in the heuristics as described below.

First Category of Heuristics

The first category of heuristics includes metrics to ascertain similarity between two proposed subject-joint locations in the same camera view at the same or different moments in time. In one embodiment, these metrics are floating point values, where higher values mean two lists of joints are likely to belong to the same subject. Consider the example embodiment of the shopping store, the metrics determine the distance between a customer's same joints in one camera from one image to the next image along the time dimension. Given a customer A in the field of view of the camera 412, the first set of metrics determines the distance between each of person A's joints from one image from the camera 412 to the next image from the camera 412. The metrics are applied to joints data structures 600 in arrays of joints data structures per image from cameras 114.

In one embodiment, two example metrics in the first category of heuristics are listed below:

-   1. The inverse of the Euclidean 2D coordinate distance (using x, y     coordinate values for a particular image from a particular camera)     between the left ankle-joint of two subjects on the floor and the     right ankle-joint of the two subjects on the floor summed together. -   2. The sum of the inverse of Euclidean 2D coordinate distance     between every pair of non-foot joints of subjects in the image     frame.

Second Category of Heuristics

The second category of heuristics includes metrics to ascertain similarity between two proposed subject-joint locations from the fields of view of multiple cameras at the same moment in time. In one embodiment, these metrics are floating point values, where higher values mean two lists of joints are likely to belong to the same subject. Consider the example embodiment of the shopping store, the second set of metrics determines the distance between a customer's same joints in image frames from two or more cameras (with overlapping fields of view) at the same moment in time.

In one embodiment, two example metrics in the second category of heuristics are listed below:

-   1. The inverse of the Euclidean 2D coordinate distance (using x, y     coordinate values for a particular image from a particular camera)     between the left ankle-joint of two subjects on the floor and the     right ankle-joint of the two subjects on the floor summed together.     The first subject's ankle-joint locations are projected to the     camera in which the second subject is visible through homographic     mapping. -   2. The sum of all pairs of joints of inverse of Euclidean 2D     coordinate distance between a line and a point, where the line is     the epipolar line of a joint of an image from a first camera having     a first subject in its field of view to a second camera with a     second subject in its field of view and the point is the joint of     the second subject in the image from the second camera.

Third Category of Heuristics

The third category of heuristics include metrics to ascertain similarity between all joints of a proposed subject-joint location in the same camera view at the same moment in time. Consider the example embodiment of the shopping store, this category of metrics determines distance between joints of a customer in one frame from one camera.

Fourth Category of Heuristics

The fourth category of heuristics includes metrics to ascertain dissimilarity between proposed subject-joint locations. In one embodiment, these metrics are floating point values. Higher values mean two lists of joints are more likely to not be the same subject. In one embodiment, two example metrics in this category include:

-   1. The distance between neck joints of two proposed subjects. -   2. The sum of the distance between pairs of joints between two     subjects.

In one embodiment, various thresholds which can be determined empirically are applied to the above listed metrics as described below:

-   1. Thresholds to decide when metric values are small enough to     consider that a joint belongs to a known subject. -   2. Thresholds to determine when there are too many potential     candidate subjects that a joint can belong to with too good of a     metric similarity score. -   3. Thresholds to determine when collections of joints over time have     high enough metric similarity to be considered a new subject,     previously not present in the real space. -   4. Thresholds to determine when a subject is no longer in the real     space. -   5. Thresholds to determine when the tracking engine 110 has made a     mistake and has confused two subjects.

The tracking engine 110 includes logic to store the sets of joints identified as subjects. The logic to identify sets of candidate joints includes logic to determine whether a candidate joint identified in images taken at a particular time corresponds with a member of one of the sets of candidate joints identified as subjects in preceding images. In one embodiment, the tracking engine 110 compares the current joint-locations of a subject with previously recorded joint-locations of the same subject at regular intervals. This comparison allows the tracking engine 110 to update the joint locations of subjects in the real space. Additionally, using this, the tracking engine 110 identifies false positives (i.e., falsely identified subjects) and removes subjects no longer present in the real space.

Consider the example of the shopping store embodiment, in which the tracking engine 110 created a customer (subject) at an earlier moment in time, however, after some time, the tracking engine 110 does not have current joint-locations for that particular customer. It means that the customer was incorrectly created. The tracking engine 110 deletes incorrectly generated subjects from the subject database 140. In one embodiment, the tracking engine 110 also removes positively identified subjects from the real space using the above described process. Consider the example of the shopping store, when a customer leaves the shopping store, the tracking engine 110 deletes the corresponding customer record from the subject database 140. In one such embodiment, the tracking engine 110 updates this customer's record in the subject database 140 to indicate that “customer has left the store”.

In one embodiment, the tracking engine 110 attempts to identify subjects by applying the foot and non-foot heuristics simultaneously. This results in “islands” of connected joints of the subjects. As the tracking engine 110 processes further arrays of joints data structures along the time and space dimensions, the size of the islands increases. Eventually, the islands of joints merge to other islands of joints forming subjects which are then stored in the subject database 140. In one embodiment, the tracking engine 110 maintains a record of unassigned joints for a predetermined period of time. During this time, the tracking engine attempts to assign the unassigned joint to existing subjects or create new multi joint entities from these unassigned joints. The tracking engine 110 discards the unassigned joints after a predetermined period of time. It is understood that, in other embodiments, different heuristics than the ones listed above are used to identify and track subjects.

In one embodiment, a user interface output device connected to the node 102 hosting the tracking engine 110 displays position of each subject in the real spaces. In one such embodiment, the display of the output device is refreshed with new locations of the subjects at regular intervals.

Subject Data Structure

The joints of the subjects are connected to each other using the metrics described above. In doing so, the tracking engine 110 creates new subjects and updates the locations of existing subjects by updating their respective joint locations. FIG. 8 shows the subject data structure 800 to store the subject. The data structure 800 stores the subject related data as a key-value dictionary. The key is a frame_number and value is another key-value dictionary where key is the camera_id and value is a list of 18 joints (of the subject) with their locations in the real space. The subject data is stored in the subject database 140. Every new subject is also assigned a unique identifier that is used to access the subject's data in the subject database 140.

In one embodiment, the system identifies joints of a subject and creates a skeleton of the subject. The skeleton is projected into the real space indicating the position and orientation of the subject in the real space. This is also referred to as “pose estimation” in the field of machine vision. In one embodiment, the system displays orientations and positions of subjects in the real space on a graphical user interface (GUI). In one embodiment, the image analysis is anonymous, i.e., a unique identifier assigned to a subject created through joints analysis does not identify personal identification details (such as names, email addresses, mailing addresses, credit card numbers, bank account numbers, driver's license number, etc.) of any specific subject in the real space.

Process Flow of Subject Tracking

A number of flowcharts illustrating logic are described herein. The logic can be implemented using processors configured as described above programmed using computer programs stored in memory accessible and executable by the processors, and in other configurations, by dedicated logic hardware, including field programmable integrated circuits, and by combinations of dedicated logic hardware and computer programs. With all flowcharts herein, it will be appreciated that many of the steps can be combined, performed in parallel, or performed in a different sequence, without affecting the functions achieved. In some cases, as the reader will appreciate, a rearrangement of steps will achieve the same results only if certain other changes are made as well. In other cases, as the reader will appreciate, a rearrangement of steps will achieve the same results only if certain conditions are satisfied. Furthermore, it will be appreciated that the flow charts herein show only steps that are pertinent to an understanding of the embodiments, and it will be understood that numerous additional steps for accomplishing other functions can be performed before, after and between those shown.

FIG. 9 is a flowchart illustrating process steps for tracking subjects. The process starts at step 902. The cameras 114 having field of view in an area of the real space are calibrated in process step 904. Video processes are performed at step 906 by image recognition engines 112 a-112 n. In one embodiment, the video process is performed per camera to process batches of image frames received from respective cameras. The output of all video processes from respective image recognition engines 112 a-112 n are given as input to a scene process performed by the tracking engine 110 at step 908. The scene process identifies new subjects and updates the joint locations of existing subjects. At step 910, it is checked if there are more image frames to be processed. If there are more image frames, the process continues at step 906, otherwise the process ends at step 914.

More detailed process steps of the process step 904 “calibrate cameras in real space” are presented in a flowchart in FIG. 10. The calibration process starts at step 1002 by identifying a (0, 0, 0) point for (x, y, z) coordinates of the real space. At step 1004, a first camera with the location (0, 0, 0) in its field of view is calibrated. More details of camera calibration are presented earlier in this application. At step 1006, a next camera with overlapping field of view with the first camera is calibrated. At step 1008, it is checked whether there are more cameras to calibrate. The process is repeated at step 1006 until all cameras 114 are calibrated.

In a next process step 1010, a subject is introduced in the real space to identify conjugate pairs of corresponding points between cameras with overlapping fields of view. Some details of this process are described above. The process is repeated for every pair of overlapping cameras at step 1012. The process ends if there are no more cameras (step 1014).

A flowchart in FIG. 11 shows more detailed steps of the “video process” step 906. At step 1102, k-contiguously timestamped images per camera are selected as a batch for further processing. In one embodiment, the value of k=6 which is calculated based on available memory for the video process in the network nodes 101 a-101 n, respectively hosting image recognition engines 112 a-112 n. In a next step 1104, the size of images is set to appropriate dimensions. In one embodiment, the images have a width of 1280 pixels, height of 720 pixels and three channels RGB (representing red, green and blue colors). At step 1106, a plurality of trained convolutional neural networks (CNN) process the images and generate arrays of joints data structures per image. The output of the CNNs are arrays of joints data structures per image (step 1108). This output is sent to a scene process at step 1110.

FIG. 12A is a flowchart showing a first part of more detailed steps for “scene process” step 908 in FIG. 9. The scene process combines outputs from multiple video processes at step 1202. At step 1204, it is checked whether a joints data structure identifies a foot joint or a non-foot joint. If the joints data structure is of a foot-joint, homographic mapping is applied to combine the joints data structures corresponding to images from cameras with overlapping fields of view at step 1206. This process identifies candidate foot joints (left and right foot joints). At step 1208 heuristics are applied on candidate foot joints identified in step 1206 to identify sets of candidate foot joints as subjects. It is checked at step 1210 whether the set of candidate foot joints belongs to an existing subject. If not, a new subject is created at step 1212. Otherwise, the existing subject is updated at step 1214.

A flowchart FIG. 12B illustrates a second part of more detailed steps for the “scene process” step 908. At step 1240, the data structures of non-foot joints are combined from multiple arrays of joints data structures corresponding to images in the sequence of images from cameras with overlapping fields of view. This is performed by mapping corresponding points from a first image from a first camera to a second image from a second camera with overlapping fields of view. Some details of this process are described above. Heuristics are applied at step 1242 to candidate non-foot joints. At step 1246 it is determined whether a candidate non-foot joint belongs to an existing subject. If so, the existing subject is updated at step 1248. Otherwise, the candidate non-foot joint is processed again at step 1250 after a predetermined time to match it with an existing subject. At step 1252 it is checked whether the non-foot joint belongs to an existing subject. If true, the subject is updated at step 1256. Otherwise, the joint is discarded at step 1254.

In an example embodiment, the processes to identify new subjects, track subjects and eliminate subjects (who have left the real space or were incorrectly generated) are implemented as part of an “entity cohesion algorithm” performed by the runtime system (also referred to as the inference system). An entity is a constellation of joints referred to as subject above. The entity cohesion algorithm identifies entities in the real space and updates locations of the joints in real space to track movement of the entity.

FIG. 14 presents an illustration of video processes 1411 and scene process 1415. In the illustrated embodiment, four video processes are shown, each processing images from one or more cameras 114. The video processes, process images as described above and identify joints per frame. In one embodiment, each video process identifies the 2D coordinates, a confidence number, a joint number and a unique ID per joint per frame. The outputs 1452 of all video processes are given as input 1453 to the scene process 1415. In one embodiment, the scene process creates a joint key-value dictionary per moment in time in which the key is the camera identifier and the value is the arrays of joints. The joints are re-projected into perspectives of cameras with overlapping fields of view. The re-projected joints are stored as a key-value dictionary. The key in this dictionary is a combination of joint id and camera id. The values in the dictionary are 2D coordinates of the joint re-projected into the target camera's perspective.

The scene process 1415 produces an output 1457 comprising a list of all subjects in the real space at a moment in time. The list includes a key-value dictionary per subject. The key is a unique identifier of a subject and the value is another key-value dictionary with the key as the frame number and the value as the camera-subject joint key-value dictionary. The camera-subject joint key-value dictionary is a per subject dictionary in which the key is the camera identifier and the value is a list of joints.

Image Analysis to Identify and Track Inventory Items Per Subject

A system and various implementations for tracking puts and takes of inventory items by subjects in an area of real space are described with reference to FIGS. 15A to 25. The system and processes are described with reference to FIG. 15A, an architectural level schematic of a system in accordance with an implementation. Because FIG. 15A is an architectural diagram, certain details are omitted to improve the clarity of the description.

Architecture of Multi-CNN Pipelines

FIG. 15A is a high-level architecture of pipelines of convolutional neural networks (also referred to as multi-CNN pipelines) processing image frames received from cameras 114 to generate shopping cart data structures for each subject in the real space. The system described here includes per camera image recognition engines as described above for identifying and tracking multi joint subjects. Alternative image recognition engines can be used, including examples in which only one “joint” is recognized and tracked per individual, or other features or other types of images data over space and time are utilized to recognize and track subjects in the real space being processed.

The multi-CNN pipelines run in parallel per camera, moving images from respective cameras to image recognition engines 112 a-112 n via circular buffers 1502 per camera. In one embodiment, image recognition engines 112 a-112 n are implemented as convolutional neural networks (CNNs) and are referred to as joint CNNs 112 a-112 n. As described in relation to FIG. 1, cameras 114 can be synchronized in time with each other, so that images are captured at the same time, or close in time, and at the same image capture rate. Images captured in all the cameras covering an area of real space at the same time, or close in time, are synchronized in the sense that the synchronized images can be identified in the processing engines as representing different views at a moment in time of subjects having fixed positions in the real space.

In one embodiment, the cameras 114 are installed in a shopping store (such as a supermarket) such that sets of cameras (two or more) with overlapping fields of view are positioned over each aisle to capture images of real space in the store. There are N cameras in the real space, however, for simplification, only one camera is shown in FIG. 17A as camera(i) where the value of i ranges from 1 to N. Each camera produces a sequence of images of real space corresponding to its respective field of view.

In one embodiment, the image frames corresponding to sequences of images from each camera are sent at the rate of 30 frames per second (fps) to respective image recognition engines 112 a-112 n. Each image frame has a timestamp, identity of the camera (abbreviated as “camera_id”), and a frame identity (abbreviated as “frame_id”) along with the image data. The image frames are stored in a circular buffer 1502 (also referred to as a ring buffer) per camera 114. Circular buffers 1502 store a set of consecutively timestamped image frames from respective cameras 114.

A joints CNN processes sequences of image frames per camera and identifies 18 different types of joints of each subject present in its respective field of view. The outputs of joints CNNs 112 a-112 n corresponding to cameras with overlapping fields of view are combined to map the location of joints from 2D image coordinates of each camera to 3D coordinates of real space. The joints data structures 800 per subject (j) where j equals 1 to x, identify locations of joints of a subject (j) in the real space. The details of subject data structure 800 are presented in FIG. 8. In one example embodiment, the joints data structure 800 is a two level key-value dictionary of joints of each subject. A first key is the frame_number and the value is a second key-value dictionary with the key as the camera_id and the value as the list of joints assigned to a subject.

The data sets comprising subjects identified by joints data structures 800 and corresponding image frames from sequences of image frames per camera are given as input to a bounding box generator 1504. The bounding box generator 1504 implements the logic to process the data sets to specify bounding boxes which include images of hands of identified subjects in images in the sequences of images. The bounding box generator 1504 identifies locations of hand joints in each source image frame per camera using locations of hand joints in the multi-joints data structures 800 corresponding to the respective source image frame. In one embodiment, in which the coordinates of the joints in subject data structure indicate location of joints in 3D real space coordinates, the bounding box generator maps the joint locations from 3D real space coordinates to 2D coordinates in the image frames of respective source images.

The bounding box generator 1504 creates bounding boxes for hand joints in image frames in a circular buffer per camera 114. In one embodiment, the bounding box is a 128 pixels (width) by 128 pixels (height) portion of the image frame with the hand joint located in the center of the bounding box. In other embodiments, the size of the bounding box is 64 pixels×64 pixels or 32 pixels×32 pixels. Form subjects in an image frame from a camera, there can be a maximum of 2m hand joints, thus 2m bounding boxes. However, in practice fewer than 2m hands are visible in an image frame because of occlusions due to other subjects or other objects. In one example embodiment, the hand locations of subjects are inferred from locations of elbow and wrist joints. For example, the right hand location of a subject is extrapolated using the location of the right elbow (identified as p1) and the right wrist (identified as p2) as extrapolation_amount*(p2−p1)+p2 where extrapolation_amount equals 0.4. In another embodiment, the joints CNN 112 a-112 n are trained using left and right hand images. Therefore, in such an embodiment, the joints CNN 112 a-112 n directly identify locations of hand joints in image frames per camera. The hand locations per image frame are used by the bounding box generator 1504 to create a bounding box per identified hand joint.

WhatCNN 1506 is a convolutional neural network trained to process the specified bounding boxes in the images to generate a classification of hands of the identified subjects. One trained WhatCNN 1506 processes image frames from one camera. In the example embodiment of the shopping store, for each hand joint in each image frame, the WhatCNN 1506 identifies whether the hand joint is empty. The WhatCNN 1506 also identifies a SKU (stock keeping unit) number of the inventory item in the hand joint, a confidence value indicating the item in the hand joint is a non-SKU item (i.e. it does not belong to the shopping store inventory) and a context of the hand joint location in the image frame.

The outputs of WhatCNN models 1506 for all cameras 114 are processed by a single WhenCNN model 1508 for a pre-determined window of time. In the example of a shopping store, the WhenCNN 1508 performs time series analysis for both hands of subjects to identify whether a subject took a store inventory item from a shelf or put a store inventory item on a shelf. A shopping cart data structure 1510 (also referred to as a log data structure including a list of inventory items) is created per subject to keep a record of the store inventory items in a shopping cart (or basket) associated with the subject.

FIG. 15B shows coordination logic module 1522 combining results of multiple WhatCNN models and giving it as input to a single WhenCNN model. As mentioned above, two or more cameras with overlapping fields of view capture images of subjects in real space. Joints of a single subject can appear in image frames of multiple cameras in respective image channel 1520. A separate WhatCNN model identifies SKUs of inventory items in hands (represented by hand joints) of subjects. The coordination logic module 1522 combines the outputs of WhatCNN models into a single consolidated input for the WhenCNN model. The WhenCNN model 1508 operates on the consolidated input to generate the shopping cart of the subject.

Detailed implementation of the system comprising multi-CNN pipelines of FIG. 15A is presented in FIGS. 16, 17, and 18. In the example of the shopping store, the system tracks puts and takes of inventory items by subjects in an area of real space. The area of real space is the shopping store with inventory items placed in shelves organized in aisles as shown in FIGS. 2 and 3. It is understood that shelves containing inventory items can be organized in a variety of different arrangements. For example, shelves can be arranged in a line with their back sides against a wall of the shopping store and the front side facing towards an open area in the real space. A plurality of cameras 114 with overlapping fields of view in the real space produce sequences of images of their corresponding fields of view. The field of view of one camera overlaps with the field of view of at least one other camera as shown in FIGS. 2 and 3.

Joints CNN—Identification and Update of Subjects

FIG. 16 is a flowchart of processing steps performed by joints CNN 112 a-112 n to identify subjects in the real space. In the example of a shopping store, the subjects are customers moving in the store in aisles between shelves and other open spaces. The process starts at step 1602. Note that, as described above, the cameras are calibrated before sequences of images from cameras are processed to identify subjects. Details of camera calibration are presented above. Cameras 114 with overlapping fields of view capture images of real space in which subjects are present (step 1604). In one embodiment, the cameras are configured to generate synchronized sequences of images. The sequences of images of each camera are stored in respective circular buffers 1502 per camera. A circular buffer (also referred to as a ring buffer) stores the sequences of images in a sliding window of time. In an embodiment, a circular buffer stores 110 image frames from a corresponding camera. In another embodiment, each circular buffer 1502 stores image frames for a time period of 3.5 seconds. It is understood, in other embodiments, the number of image frames (or the time period) can be greater than or less than the example values listed above.

I Joints CNNs 112 a-112 n, receive sequences of image frames from corresponding cameras 114 (step 1606). Each joints CNN processes batches of images from a corresponding camera through multiple convolution network layers to identify joints of subjects in image frames from corresponding camera. The architecture and processing of images by an example convolutional neural network is presented FIG. 5. As cameras 114 have overlapping fields of view, the joints of a subject are identified by more than one joints-CNN. The two dimensional (2D) coordinates of joints data structures 600 produced by joints-CNN are mapped to three dimensional (3D) coordinates of the real space to identify joints locations in the real space. Details of this mapping are presented in discussion of FIG. 7 in which the tracking engine 110 translates the coordinates of the elements in the arrays of joints data structures corresponding to images in different sequences of images into candidate joints having coordinates in the real space.

The joints of a subject are organized in two categories (foot joints and non-foot joints) for grouping the joints into constellations, as discussed above. The left and right-ankle joint type in the current example, are considered foot joints for the purpose of this procedure. At step 1608, heuristics are applied to assign a candidate left foot joint and a candidate right foot joint to a set of candidate joints to create a subject. Following this, at step 1610, it is determined whether the newly identified subject already exists in the real space. If not, then a new subject is created at step 1614, otherwise, the existing subject is updated at step 1612.

Other joints from the galaxy of candidate joints can be linked to the subject to build a constellation of some or all of the joint types for the created subject. At step 1616, heuristics are applied to non-foot joints to assign those to the identified subjects. The global metric calculator 702 calculates the global metric value and attempts to minimize the value by checking different combinations of non-foot joints. In one embodiment, the global metric is a sum of heuristics organized in four categories as described above.

The logic to identify sets of candidate joints comprises heuristic functions based on physical relationships among joints of subjects in real space to identify sets of candidate joints as subjects. At step 1618, the existing subjects are updated using the corresponding non-foot joints. If there are more images for processing (step 1620), steps 1606 to 1618 are repeated, otherwise the process ends at step 1622. A first data sets are produced at the end of the process described above. The first data sets identify subject and the locations of the identified subjects in the real space. In one embodiment, the first data sets are presented above in relation to FIG. 15A as joints data structures 800 per subject.

WhatCNN—Classification of Hand Joints

FIG. 17 is a flowchart illustrating processing steps to identify inventory items in hands of subjects identified in the real space. In the example of a shopping store, the subjects are customers in the shopping store. As the customers move in the aisles and opens spaces, they pick up inventory items stocked in the shelves and put the items in their shopping cart or basket. The image recognition engines identify subjects in the sets of images in the sequences of images received from the plurality of cameras. The system includes the logic to process sets of images in the sequences of images that include the identified subjects to detect takes of inventory items by identified subjects and puts of inventory items on the shelves by identified subjects.

In one embodiment, the logic to process sets of images includes, for the identified subjects, logic to process images to generate classifications of the images of the identified subjects. The classifications include whether the identified subject is holding an inventory item. The classifications include a first nearness classification indicating a location of a hand of the identified subject relative to a shelf. The classifications include a second nearness classification indicating a location a hand of the identified subject relative to a body of the identified subject. The classifications further include a third nearness classification indicating a location a hand of the identified subject relative to a basket associated with an identified subject. Finally, the classifications include an identifier of a likely inventory item.

In another embodiment, the logic to process sets of images includes, for the identified subjects, logic to identify bounding boxes of data representing hands in images in the sets of images of the identified subjects. The data in the bounding boxes is processed to generate classifications of data within the bounding boxes for the identified subjects. In such an embodiment, the classifications include whether the identified subject is holding an inventory item. The classifications include a first nearness classification indicating a location of a hand of the identified subject relative to a shelf. The classifications include a second nearness classification indicating a location of a hand of the identified subject relative to a body of the identified subject. The classifications include a third nearness classification indicating a location of a hand of the identified subject relative to a basket associated with an identified subject. Finally, the classifications include an identifier of a likely inventory item.

The process starts at step 1702. At step 1704, locations of hands (represented by hand joints) of subjects in image frames are identified. The bounding box generator 1504 identifies hand locations of subjects per frame from each camera using joint locations identified in the first data sets generated by joints CNNs 112 a-112 n as described in FIG. 18. Following this, at step 1706, the bounding box generator 1504 processes the first data sets to specify bounding boxes which include images of hands of identified multi joint subjects in images in the sequences of images. Details of bounding box generator are presented above in discussion of FIG. 15A.

A second image recognition engine receives sequences of images from the plurality of cameras and processes the specified bounding boxes in the images to generate a classification of hands of the identified subjects (step 1708). In one embodiment, each of the image recognition engines used to classify the subjects based on images of hands comprises a trained convolutional neural network referred to as a WhatCNN 1506. WhatCNNs are arranged in multi-CNN pipelines as described above in relation to FIG. 15A. In one embodiment, the input to a WhatCNN is a multi-dimensional array B×W×H×C (also referred to as a B×W×H×C tensor). “B” is the batch size indicating the number of image frames in a batch of images processed by the WhatCNN. “W” and “H” indicate the width and height of the bounding boxes in pixels, “C” is the number of channels. In one embodiment, there are 30 images in a batch (B=30), so the size of the bounding boxes is 32 pixels (width) by 32 pixels (height). There can be six channels representing red, green, blue, foreground mask, forearm mask and upperarm mask, respectively. The foreground mask, forearm mask and upperarm mask are additional and optional input data sources for the WhatCNN in this example, which the CNN can include in the processing to classify information in the RGB image data. The foreground mask can be generated using mixture of Gaussian algorithms, for example. The forearm mask can be a line between the wrist and elbow providing context produced using information in the Joints data structure. Likewise the upperarm mask can be a line between the elbow and shoulder produced using information in the Joints data structure. Different values of B, W, H and C parameters can be used in other embodiments. For example, in another embodiment, the size of the bounding boxes is larger e.g., 64 pixels (width) by 64 pixels (height) or 128 pixels (width) by 128 pixels (height).

Each WhatCNN 1506 processes batches of images to generate classifications of hands of the identified subjects. The classifications include whether the identified subject is holding an inventory item. The classifications include one or more classifications indicating locations of the hands relative to the shelf and relative to the subject, usable to detect puts and takes. In this example, a first nearness classification indicates a location of a hand of the identified subject relative to a shelf. The classifications include in this example a second nearness classification indicating a location a hand of the identified subject relative to a body of the identified subject, where a subject may hold an inventory item during shopping. The classifications in this example further include a third nearness classification indicating a location of a hand of the identified subject relative to a basket associated with an identified subject, where a “basket” in this context is a bag, a basket, a cart or other object used by the subject to hold the inventory items during shopping. Finally, the classifications include an identifier of a likely inventory item. The final layer of the WhatCNN 1506 produces logits which are raw values of predictions. The logits are represented as floating point values and further processed, as described below, for generating a classification result. In one embodiment, the outputs of the WhatCNN model, include a multi-dimensional array B×L (also referred to as a B×L tensor). “B” is the batch size, and “L=N+5” is the number of logits output per image frame. “N” is the number of SKUs representing “N” unique inventory items for sale in the shopping store.

The output “L” per image frame is a raw activation from the WhatCNN 1506. Logits “L” are processed at step 1710 to identify inventory item and context. The first “N” logits represent confidence that the subject is holding one of the “N” inventory items. Logits “L” include an additional five (5) logits which are explained below. The first logit represents confidence that the image of the item in hand of the subject is not one of the store SKU items (also referred to as non-SKU item). The second logit indicates a confidence whether the subject is holding an item or not. A large positive value indicates that WhatCNN model has a high level of confidence that the subject is holding an item. A large negative value indicates that the model is confident that the subject is not holding any item. A close to zero value of the second logit indicates that WhatCNN model is not confident in predicting whether the subject is holding an item or not.

The next three logits represent first, second and third nearness classifications, including a first nearness classification indicating a location of a hand of the identified subject relative to a shelf, a second nearness classification indicating a location of a hand of the identified subject relative to a body of the identified subject, and a third nearness classification indicating a location of a hand of the identified subject relative to a basket associated with an identified subject. Thus, the three logits represent context of the hand location with one logit each indicating confidence that the context of the hand is near to a shelf, near to a basket (or a shopping cart), or near to a body of the subject. In one embodiment, the WhatCNN is trained using a training dataset containing hand images in the three contexts: near to a shelf, near to a basket (or a shopping cart), and near to a body of a subject. In another embodiment, a “nearness” parameter is used by the system to classify the context of the hand. In such an embodiment, the system determines the distance of a hand of the identified subject to the shelf, basket (or a shopping cart), and body of the subject to classify the context.

The output of a WhatCNN is “L” logits comprised of N SKU logits, 1 Non-SKU logit, 1 holding logit, and 3 context logits as described above. The SKU logits (first N logits) and the non-SKU logit (the first logit following the N logits) are processed by a softmax function. As described above with reference to FIG. 5, the softmax function transforms a K-dimensional vector of arbitrary real values to a K-dimensional vector of real values in the range [0, 1] that add up to 1. A softmax function calculates the probabilities distribution of the item over N+1 items. The output values are between 0 and 1, and the sum of all the probabilities equals one. The softmax function (for multi-class classification) returns the probabilities of each class. The class that has the highest probability is the predicted class (also referred to as target class).

The holding logit is processed by a sigmoid function. The sigmoid function takes a real number value as input and produces an output value in the range of 0 to 1. The output of the sigmoid function identifies whether the hand is empty or holding an item. The three context logits are processed by a softmax function to identify the context of the hand joint location. At step 1712, it is checked if there are more images to process. If true, steps 1704-1710 are repeated, otherwise the process ends at step 1714.

WhenCNN—Time Series Analysis to Identify Puts and Takes of Items

In one embodiment, the system implements logic to perform time sequence analysis over the classifications of subjects to detect takes and puts by the identified subjects. The outputs of WhatCNNs 1506 in the multi-CNN pipelines are given as input to the WhenCNN 1508 which processes these inputs to detect takes and puts by the identified subjects. Finally, the system includes logic, responsive to the detected takes and puts, to generate a log data structure including a list of inventory items for each identified subject. In the example of a shopping store, the log data structure is also referred to as a shopping cart data structure 1510 per subject.

FIG. 18 presents a process implementing the logic to generate a shopping cart data structure per subject. The process starts at step 1802. The input to WhenCNN 1508 is prepared at step 1804. The input to the WhenCNN is a multi-dimensional array B×C×T×Cams, where B is the batch size, C is the number of channels, T is the number of frames considered for a window of time, and Cams is the number of cameras 114. In one embodiment, the batch size “B” is 64 and the value of “T” is 110 image frames or the number of image frames in 3.5 seconds of time.

For each subject identified per image frame, per camera, a list of 10 logits per hand joint (20 logits for both hands) is produced. The holding and context logits are part of the “L” logits generated by WhatCNN 1506 as described above.

-   -   [         -   holding, #1 logit         -   context, #3 logits         -   slice_dot(sku, log_sku), #1 logit         -   slice_dot(sku, log_other_sku), #1 logit         -   slice_dot(sku, roll(log_sku, −30)), #1 logit         -   slice_dot(sku, roll(log_sku, 30)), #1 logit         -   slice_dot(sku, roll(log_other_sku, −30)), #1 logit         -   slice_dot(sku, roll(log_other_sku, 30)) #1 logit     -   ]

The above data structure is generated for each hand in an image frame and also includes data about the other hand of the same subject. For example, if data is for the left hand joint of a subject, corresponding values for the right hand are included as “other” logits. The fifth logit (item number 3 in the list above referred to as log_sku) is the log of SKU logit in “L” logits described above. The sixth logit is the log of SKU logit for other hand. A “roll” function generates the same information before and after the current frame. For example, the seventh logit (referred to as roll(log_sku, −30)) is the log of the SKU logit, 30 frames earlier than the current frame. The eighth logit is the log of the SKU logits for the hand, 30 frames later than the current frame. The ninth and tenth data values in the list are similar data for the other hand 30 frames earlier and 30 frames later than the current frame. A similar data structure for the other hand is also generated, resulting in a total of 20 logits per subject per image frame per camera. Therefore, the number of channels in the input to the WhenCNN is 20 (i.e. C=20 in the multi-dimensional array B×C×T×Cams).

For all image frames in the batch of image frames (e.g., B=64) from each camera, similar data structures of 20 hand logits per subject, identified in the image frame, are generated. A window of time (T=3.5 seconds or 110 image frames) is used to search forward and backward image frames in the sequence of image frames for the hand joints of subjects. At step 1806, the 20 hand logits per subject per frame are consolidated from multi-CNN pipelines. In one embodiment, the batch of image frames (64) can be imagined as a smaller window of image frames placed in the middle of a larger window of image frame 110 with additional image frames for forward and backward search on both sides. The input B×C×T×Cams to WhenCNN 1508 is composed of 20 logits for both hands of subjects identified in batch “B” of image frames from all cameras 114 (referred to as “Cams”). The consolidated input is given to a single trained convolutional neural network referred to as WhenCNN model 1508.

The output of the WhenCNN model comprises of 3 logits, representing confidence in three possible actions of an identified subject: taking an inventory item from a shelf, putting an inventory item back on the shelf, and no action. The three output logits are processed by a softmax function to predict an action performed. The three classification logits are generated at regular intervals for each subject and results are stored per person along with a time stamp. In one embodiment, the three logits are generated every twenty frames per subject. In such an embodiment, at an interval of every 20 image frames per camera, a window of 110 image frames is formed around the current image frame.

A time series analysis of these three logits per subject over a period of time is performed (step 1808) to identify true events and their time of occurrence. A non-maximum suppression (NMS) algorithm is used for this purpose. As one event (i.e. put or take of an item by a subject) is detected by WhenCNN 1508 multiple times (both from the same camera and from multiple cameras), the NMS removes superfluous events for a subject. NMS is a rescoring technique comprising two main tasks: “matching loss” that penalizes superfluous detections and “joint processing” of neighbors to know if there is a better detection close-by.

The true events of takes and puts for each subject are further processed by calculating an average of the SKU logits for 30 image frames prior to the image frame with the true event. Finally, the arguments of the maxima (abbreviated arg max or argmax) is used to determine the largest value. The inventory item classified by the argmax value is used to identify the inventory item put or take from the shelf. The inventory item is added to a log of SKUs (also referred to as shopping cart or basket) of respective subjects in step 1810. The process steps 1804 to 1810 are repeated, if there is more classification data (checked at step 1812). Over a period of time, this processing results in updates to the shopping cart or basket of each subject. The process ends at step 1814.

WhatCNN with Scene and Video Processes

FIG. 19 presents an embodiment of the system in which data from scene process 1415 and video processes 1411 is given as input to WhatCNN model 1506 to generate hand image classifications. Note that the output of each video process is given to a separate WhatCNN model. The output from the scene process 1415 is a joints dictionary. In this dictionary, keys are unique joint identifiers and values are unique subject identifiers with which the joint is associated. If no subject is associated with a joint, then it is not included in the dictionary. Each video process 1411 receives a joints dictionary from the scene process and stores it into a ring buffer that maps frame numbers to the returned dictionary. Using the returned key-value dictionary, the video processes select subsets of the image at each moment in time that are near hands associated with identified subjects. These portions of image frames around hand joints can be referred to as region proposals.

In the example of a shopping store, a region proposal is the frame image of hand location from one or more cameras with the subject in their corresponding fields of view. A region proposal is generated by every camera in the system. It includes empty hands as well as hands carrying shopping store inventory items and items not belonging to shopping store inventory. Video processes select portions of image frames containing hand joint per moment in time. Similar slices of foreground masks are generated. The above (image portions of hand joints and foreground masks) are concatenated with the joints dictionary (indicating subjects to whom respective hand joints belong) to produce a multi-dimensional array. This output from video processes is given as input to the WhatCNN model.

The classification results of the WhatCNN model are stored in the region proposal data structures (produced by video processes). All regions for a moment in time are then given back as input to the scene process. The scene process stores the results in a key-value dictionary, where the key is a subject identifier and the value is a key-value dictionary, where the key is a camera identifier and the value is a region's logits. This aggregated data structure is then stored in a ring buffer that maps frame numbers to the aggregated structure for each moment in time.

WhenCNN with Scene and Video Processes

FIG. 20 presents an embodiment of the system in which the WhenCNN 1508 receives output from a scene process following the hand image classifications performed by the WhatCNN models per video process as explained in FIG. 19. Region proposal data structures for a period of time e.g., for one second, are given as input to the scene process. In one embodiment, in which cameras are taking images at the rate of 30 frames per second, the input includes 30 time periods and corresponding region proposals. The scene process reduces 30 region proposals (per hand) to a single integer representing the inventory item SKU. The output of the scene process is a key-value dictionary in which the key is a subject identifier and the value is the SKU integer.

The WhenCNN model 1508 performs a time series analysis to determine the evolution of this dictionary over time. This results in identification of items taken from shelves and put on shelves in the shopping store. The output of the WhenCNN model is a key-value dictionary in which the key is the subject identifier and the value is logits produced by the WhenCNN. In one embodiment, a set of heuristics 2002 is used to determine the shopping cart data structure 1510 per subject. The heuristics are applied to the output of the WhenCNN, joint locations of subjects indicated by their respective joints data structures, and planograms. The planograms are precomputed maps of inventory items on shelves. The heuristics 2002 determine, for each take or put, whether the inventory item is put on a shelf or taken from a shelf, whether the inventory item is put in a shopping cart (or a basket) or taken from the shopping cart (or the basket) or whether the inventory item is close to the identified subject's body.

Example Architecture of What-CNN Model

FIG. 21 presents an example architecture of WhatCNN model 1506. In this example architecture, there are a total of 26 convolutional layers. The dimensionality of different layers in terms of their respective width (in pixels), height (in pixels) and number of channels is also presented. The first convolutional layer 2113 receives input 2111 and has a width of 64 pixels, height of 64 pixels and has 64 channels (written as 64×64×64). The details of input to the WhatCNN are presented above. The direction of arrows indicates flow of data from one layer to the following layer. The second convolutional layer 2115 has a dimensionality of 32×32×64. Followed by the second layer, there are eight convolutional layers (shown in box 2117) each with a dimensionality of 32×32×64. Only two layers 2119 and 2121 are shown in the box 2117 for illustration purposes. This is followed by another eight convolutional layers 2123 of 16×16×128 dimensions. Two such convolutional layers 2125 and 2127 are shown in FIG. 21. Finally, the last eight convolutional layers 2129, have a dimensionality of 8×8×256 each. Two convolutional layers 2131 and 2133 are shown in the box 2129 for illustration.

There is one fully connected layer 2135 with 256 inputs from the last convolutional layer 2133 producing N+5 outputs. As described above, “N” is the number of SKUs representing “N” unique inventory items for sale in the shopping store. The five additional logits include the first logit representing confidence that item in the image is a non-SKU item, and the second logit representing confidence whether the subject is holding an item. The next three logits represent first, second and third nearness classifications, as described above. The final output of the WhatCNN is shown at 2137. The example architecture uses batch normalization (BN). Distribution of each layer in a convolutional neural network (CNN) changes during training and it varies from one layer to another. This reduces convergence speed of the optimization algorithm. Batch normalization (Ioffe and Szegedy 2015) is a technique to overcome this problem. ReLU (Rectified Linear Unit) activation is used for each layer's non-linearity except for the final output where softmax is used.

FIGS. 22, 23, and 24 are graphical visualizations of different parts of an implementation of WhatCNN 1506. The figures are adapted from graphical visualizations of a WhatCNN model generated by TensorBoard™. TensorBoard™ is a suite of visualization tools for inspecting and understanding deep learning models e.g., convolutional neural networks.

FIG. 22 shows a high level architecture of the convolutional neural network model that detects a single hand (“single hand” model 2210). WhatCNN model 1506 comprises two such convolutional neural networks for detecting left and right hands, respectively. In the illustrated embodiment, the architecture includes four blocks referred to as block0 2216, block1 2218, block2 2220, and block3 2222. A block is a higher-level abstraction and comprises multiple nodes representing convolutional layers. The blocks are arranged in a sequence from lower to higher such that output from one block is input to a successive block. The architecture also includes a pooling layer 2214 and a convolution layer 2212. In between the blocks, different non-linearities can be used. In the illustrated embodiment, a ReLU non-linearity is used as described above.

In the illustrated embodiment, the input to the single hand model 2210 is a B×W×H×C tensor defined above in description of WhatCNN 1506. “B” is the batch size, “W” and “H” indicate the width and height of the input image, and “C” is the number of channels. The output of the single hand model 2210 is combined with a second single hand model and passed to a fully connected network.

During training, the output of the single hand model 2210 is compared with ground truth. A prediction error calculated between the output and the ground truth is used to update the weights of convolutional layers. In the illustrated embodiment, stochastic gradient descent (SGD) is used for training WhatCNN 1506.

FIG. 23 presents further details of the block0 2216 of the single hand convolutional neural network model of FIG. 22. It comprises four convolutional layers labeled as conv0 in box 2310, conv1 2318, conv2 2320, and conv3 2322. Further details of the convolutional layer conv0 are presented in the box 2310. The input is processed by a convolutional layer 2312. The output of the convolutional layer is processed by a batch normalization layer 2314. ReLU non-linearity 2316 is applied to the output of the batch normalization layer 2314. The output of the convolutional layer conv0 is passed to the next layer conv1 2318. The output of the final convolutional layer conv3 is processed through an addition operation 2324. This operation sums the output from the layer conv3 2322 to unmodified input coming through a skip connection 2326. It has been shown by He et al. in their paper titled, “Identity mappings in deep residual networks” (published at https://arxiv.org/pdf/1603.05027.pdf on Jul. 25, 2016) that forward and backward signals can be directly propagated from one block to any other block. The signal propagates unchanged through the convolutional neural network. This technique improves training and test performance of deep convolutional neural networks.

As described in FIG. 21, the output of convolutional layers of a WhatCNN is processed by a fully connected layer. The outputs of two single hand models 2210 are combined and passed as input to a fully connected layer. FIG. 24 is an example implementation of a fully connected layer (FC) 2410. The input to the FC layer is processed by a reshape operator 2412. The reshape operator changes the shape of the tensor before passing it to a next layer 2420. Reshaping includes flattening the output from the convolutional layers i.e., reshaping the output from a multi-dimensional matrix to a one-dimensional matrix or a vector. The output of the reshape operator 2412 is passed to a matrix multiplication operator labelled as MatMul 2422. The output from the MatMul 2422 is passed to a matrix plus addition operator labelled as xw_plus_b 2424. For each input “x”, the operator 2424 multiplies the input by a matrix “w” and a vector “b” to produce the output. “w” is a trainable parameter associated with the input “x” and “b” is another trainable parameter which is called bias or intercept. The output 2426 from the fully connecter layer 2410 is a B×L tensor as explained above in the description of WhatCNN 1506. “B” is the batch size, and “L=N+5” is the number of logits output per image frame. “N” is the number of SKUs representing “N” unique inventory items for sale in the shopping store.

Training of WhatCNN Model

A training data set of images of hands holding different inventory items in different contexts, as well as empty hands in different contexts is created. To achieve this, human actors hold each unique SKU inventory item in multiple different ways, at different locations of a test environment. The context of their hands range from being close to the actor's body, being close to the store's shelf, and being close to the actor's shopping cart or basket. The actor performs the above actions with an empty hand as well. This procedure is completed for both left and right hands. Multiple actors perform these actions simultaneously in the same test environment to simulate the natural occlusion that occurs in real shopping stores.

Cameras 114 takes images of actors performing the above actions. In one embodiment, twenty cameras are used in this process. The joints CNNs 112 a-112 n and the tracking engine 110 process the images to identify joints. The bounding box generator 1504 creates bounding boxes of hand regions similar to production or inference. Instead of classifying these hand regions via the WhatCNN 1506, the images are saved to a storage disk. Stored images are reviewed and labelled. An image is assigned three labels: the inventory item SKU, the context, and whether the hand is holding something or not. This process is performed for a large number of images (up to millions of images).

The image files are organized according to data collection scenes. The naming convention for image file identifies content and context of the images. FIG. 25 shows an image file name in an example embodiment. A first part of the file name, referred to by a numeral 2502, identifies the data collection scene and also includes the timestamp of the image. A second part 2504 of the file name identifies the source camera. In the example shown in FIG. 25, the image is captured by “camera 4”. A third part 2506 of the file name identifies the frame number from the source camera. In the illustrated example, the file name indicates it is the 94,600^(th) image frame from camera 4. A fourth part 2508 of the file name identifies ranges of x and y coordinates region in the source image frame from which this hand region image is taken. In the illustrated example, the region is defined between x coordinate values from pixel 117 to 370 and y coordinates values from pixels 370 and 498. A fifth part 2510 of the file name identifies the person id of the actor in the scene. In the illustrated example, the person in the scene has an id “3”. Finally, a sixth part 2512 of the file name identifies the SKU number (item=68) of the inventory item, identified in the image.

In training mode of the WhatCNN 1506, forward passes and backpropagations are performed as opposed to production mode in which only forward passes are performed. During training, the WhatCNN generates a classification of hands of the identified subjects in a forward pass. The output of the WhatCNN is compared with the ground truth. In the backpropagation, a gradient for one or more cost functions is calculated. The gradient(s) are then propagated to the convolutional neural network (CNN) and the fully connected (FC) neural network so that the prediction error is reduced causing the output to be closer to the ground truth. In one embodiment, stochastic gradient descent (SGD) is used for training WhatCNN 1506.

In one embodiment, 64 images are randomly selected from the training data and augmented. The purpose of image augmentation is to diversify the training data resulting in better performance of models. The image augmentation includes random flipping of the image, random rotation, random hue shifts, random Gaussian noise, random contrast changes, and random cropping. The amount of augmentation is a hyperparameter and is tuned through hyperparameter search. The augmented images are classified by WhatCNN 1506 during training. The classification is compared with ground truth and coefficients or weights of WhatCNN 1506 are updated by calculating gradient loss function and multiplying the gradient with a learning rate. The above process is repeated many times (e.g., approximately 1000 times) to form an epoch. Between 50 to 200 epochs are performed. During each epoch, the learning rate is slightly decreased following a cosine annealing schedule.

Training of WhenCNN Model

Training of WhenCNN 1508 is similar to the training of WhatCNN 1506 described above, using backpropagations to reduce prediction error. Actors perform a variety of actions in the training environment. In the example embodiment, the training is performed in a shopping store with shelves stocked with inventory items. Examples of actions performed by actors include, take an inventory item from a shelf, put an inventory item back on a shelf, put an inventory item into a shopping cart (or a basket), take an inventory item back from the shopping cart, swap an item between left and right hands, put an inventory item into the actor's nook. A nook refers to a location on the actor's body that can hold an inventory item besides the left and right hands. Some examples of nook include, an inventory item squeezed between a forearm and upper arm, squeezed between a forearm and a chest, squeezed between neck and a shoulder.

The cameras 114 record videos of all actions described above during training. The videos are reviewed and all image frames are labelled indicating the timestamp and the action performed. These labels are referred to as action labels for respective image frames. The image frames are processed through the multi-CNN pipelines up to the WhatCNNs 1506 as described above for production or inference. The output of WhatCNNs along with the associated action labels are then used to train the WhenCNN 1508, with the action labels acting as ground truth. Stochastic gradient descent (SGD) with a cosine annealing schedule is used for training as described above for training of WhatCNN 1506.

In addition to image augmentation (used in training of WhatCNN), temporal augmentation is also applied to image frames during training of the WhenCNN. Some examples include mirroring, adding Gaussian noise, swapping the logits associated with left and right hands, shortening the time, shortening the time series by dropping image frames, lengthening the time series by duplicating frames, and dropping the data points in the time series to simulate spottiness in the underlying model generating input for the WhenCNN. Mirroring includes reversing the time series and respective labels, for example a put action becomes a take action when reversed.

Particular Implementations

In various embodiments, the system for tracking puts and takes of inventory items by subjects in an area of real space described above also includes one or more of the following features.

1. Region Proposals

A region proposal is the frame image of hand location from all different cameras covering the person. A region proposal is generated by every camera in the system. It includes empty hands as well as hands carrying store items.

1.1 the WhatCNN Model

A region proposal can be used as input to image classification using a deep learning algorithm. This classification engine is called a “WhatCNN” model. It is an in-hand classification model. It classifies the things that are in hands. In-hand image classification can operate even though parts of the object are occluded by the hand. Smaller items may be occluded up to 90% by the hand. The region for image analysis by the WhatCNN model is intentionally kept small in some embodiments because it is computationally expensive. Each camera can have a dedicated GPU. This is performed for every hand image from every camera for every frame. In addition to the above image analysis by the WhatCNN model, a confidence weight is also assigned to that image (one camera, one point in time). The classification algorithm outputs logits over the entire list of stock keeping units (SKUs) to produce a product and service identification code list of the store for n items and one additional for an empty hand (n+1).

The scene process now communicates back its results to each video process by sending a key-value dictionary to each video. Here keys are unique joint IDs and values are unique person IDs with which the joint is associated. If no person was found associated with the joint, then it is not included in the dictionary.

Each video process receives the key-value dictionary from the scene process and stores it into a ring buffer that maps frame numbers to the returned dictionary.

Using the returned key-value dictionary, the video selects subsets of the image at each moment in time that are near hands associated with known people. These regions are numpy slices. We also take a similar slice around foreground masks and the raw output feature arrays of the Joints CNN. These combined regions are concatenated together into a single multidimensional numpy array and stored in a data structure that holds the numpy array as well as the person ID with which the region is associated and which hand from the person the region came from.

All proposed regions are then fed into a FIFO queue. This queue takes in regions and pushes their numpy array into memory on the GPU.

As arrays arrive on the GPU they are fed into a CNN dedicated to classification, referred to as a WhatCNN. The output of this CNN is a flat array of floats of size N+1, where N is the number of unique SKUs in the store, and the final class represents the nil class, or empty hand. The floats in this array are referred to as logits.

The results of the WhatCNN are stored back into the region data structure.

All regions for a moment in time are then sent from each video process back to the scene process.

The scene process receives all regions from all videos at a moment in time and stores the results in a key-value dictionary, where the key is a person ID and the value is a key-value dictionary, where the key is a camera ID and the value is a region's logits.

This aggregated data structure is then stored in a ring buffer that maps frame numbers to the aggregated structure for each moment in time.

1.2 the WhenCNN Model

The images from different cameras processed by the WhatCNN model are combined over a period of time (multiple cameras over a period of time). An additional input to this model is hand location in 3D space, triangulated from multiple cameras. Another input to this algorithm is the distance of a hand from a planogram of the store. In some embodiments, the planogram can be used to identify if the hand is close to a shelf containing a particular item (e.g. cheerios boxes). Another input to this algorithm is the foot location on the store.

In addition to object classification using SKU, the second classification model uses time series analysis to determine whether the object was picked up from the shelf or placed on the shelf. The images are analyzed over a period of time to make the determination of whether the object that was in the hand in earlier image frames has been put back in the shelf or has been picked up from the shelf.

For a one second time (30 frames per second) period and three cameras, the system will have 90 classifications outputs for the same hand plus confidences. This combined image analysis dramatically increases the probability of correctly identifying the object in the hand. The analysis over time improves the quality of output despite some very low confidence level outputs of individual frames. This step can take the output confidence from for example, 80% accuracy to 95% accuracy.

This model also includes output from the shelf model as its input to identify what object this person has picked.

The scene process waits for 30 or more aggregated structures to accumulate, representing at least a second of real time, and then performs a further analysis to reduce the aggregated structure down to a single integer for each person ID-hand pair, where the integer is a unique ID representing a SKU in the store. For a moment in time this information is stored in a key-value dictionary where keys are person ID-hand pairs, and values are the SKU integer. This dictionary is stored over time in a ring buffer that maps frame numbers to each dictionary for that moment in time.

An additional analysis can be then performed looking at how this dictionary changes over time in order to identify at what moments a person takes something and what it is they take. This model (WhenCNN) emits SKU logits as well as logits for each Boolean question: was something taken? was something placed?

The output of the WhenCNN is stored in a ring buffer that maps frame numbers to a key-value dictionary where keys are person IDs and values are the extended logits emitted by the WhenCNN.

A further collection of heuristics is then run on the stored results of both the WhenCNN and the stored joint locations of people, as well as a precomputed map of items on the store shelf. This collection of heuristics determines where takes and puts result in items being added to or removed from. For each take/put the heuristics determine if the take or put was from or to a shelf, from or to a basket, or from or to a person. The output is an inventory for each person, stored as an array where the array value at a SKU's index is the number of those SKUs a person has.

As a shopper nears the exit of a store the system can send the inventory list to the shopper's phone. The phone then displays the user's inventory and asks for confirmation to charge their stored credit card information. If the user accepts, their credit card will be charged. If they do not have a credit card known in the system, they will be asked to provide credit card information.

Alternatively, the shopper may also approach an in-store kiosk. The system identifies when the shopper is near the kiosk and will send a message to the kiosk to display the inventory of the shopper. The kiosk asks the shopper to accept the charges for the inventory. If the shopper accepts, they may then swipe their credit card or insert cash to pay. FIG. 16 presents an illustration of the WhenCNN model for region proposals.

2. Misplaced Items

This feature identifies misplaced items when they are placed back by a person on a random shelf. This causes problems in object identification because the foot and hand location with respect to the planogram will be incorrect. Therefore, the system builds up a modified planogram over time. Based on prior time series analysis, the system is able to determine if a person has placed an item back in the shelf. Next time, when an object is picked up from that shelf location, the system knows that there is at least one misplaced item in that hand location. Correspondingly, the algorithm will have some confidence that the person can pick up the misplaced item from that shelf. If the misplaced item is picked up from the shelf, the system subtracts that item from that location and therefore, the shelf does not have that item anymore. The system can also inform a clerk about a misplaced item via an app so that the clerk can move that item to its correct shelf.

3. Semantic Diffing (Shelf Model)

A background subtraction algorithm may be used to identify changes to items (items removed or placed) on the shelves. This is based on changes at the pixel level. If there are persons in front of the shelf, then the algorithm stops so that it does not take into account pixel changes due to presence of persons. Background subtraction is a noisy process. Therefore, a cross-camera analysis is conducted. If enough cameras agree that there is a “semantically meaningful” change in the shelf, then the system records that there is a change in that part of the shelf.

The next step is to identify whether that change is a “put” or a “get” change. For this, the time series analysis of the second classification model is used. A region proposal for that particular part of the shelf is generated and passed through the deep learning algorithm. This is easier than in-hand image analysis because the object is not occluded inside a hand. A fourth input is given to the algorithm in addition to the three typical RGB inputs. The fourth channel is the background information. The output of the shelf or semantic diffing is input again to the second classification model (time-series analysis model).

Semantic diffing includes the following steps:

-   1. Images from a camera are compared to earlier images from the same     camera. -   2. Each corresponding pixel between the two images is compared via a     Euclidean distance in RGB space. -   3. Distances above a certain threshold are marked, resulting in a     new image of just marked pixels. -   4. A collection of image morphology filters are used to remove noise     from the marked image. -   5. We then search for large collections of marked pixels and form     bounding boxes around them. -   6. For each bounding box we then look at the original pixels in the     two images to get two image snapshots. -   7. These two image snapshots are then pushed into a CNN trained to     classify whether the image region represents an item being taken or     an item being placed and what the item is.

4. Store Audit

An inventory of each shelf is maintained by the system. It is updated as items are picked up by the customers. At any point in time, the system is able to generate an audit of store inventory.

5. Multiple Items in Hand

Different images are used for multiple items. Two items in the hand are treated differently as compared to one. Some algorithms can predict only one item but not multiple numbers of an item. Therefore, the CNNs are trained so the algorithms for “two” quantities of the items can be executed separately from a single item in the hand.

6. Data Collection System

Predefined shopping scripts are used to collect good quality data of images. These images are used for training of algorithms.

6.1 Shopping Scripts

Data collection includes the following steps:

-   1. A script is automatically generated telling a human actor what     actions to take. -   2. These actions are randomly sampled from a collection of actions     including: take item X, place item X, hold item X for Y seconds. -   3. While performing these actions the actors move and orient     themselves in as many ways as possible while still succeeding at the     given action. -   4. During the sequences of actions a collection of cameras record     the actors from many perspectives. -   5. After the actors have finished the script, the camera videos are     bundled together and saved along with the original script. -   6. The script serves as an input label to machine learning models     (such as the CNNs) that train on the videos of actors.

7. Product Line

The system and parts thereof can be used for cashier-less checkout, supported by the following apps.

7.1 Store App

The Store App has several main capabilities; providing data analytic visualizations, supporting loss prevention, and providing a platform to assist customers by showing the retailer where people are in the store and what merchandise they have collected. Permission levels and app access to employees can be dictated at the retailer's discretion.

7.1.1 Standard Analytics

Data is collected by the platform and can be used in a variety of ways.

-   1. The derivative data is used to perform various kinds of analytics     on stores, the shopping experiences they provide, and customer     interactions with products, environment, and other people.     -   a. The data is stored and used in the background to perform         analyses of the store and customer interactions. The Store App         will display some of the visualizations of this data to         retailers. Other data is stored and queried when the data point         is desired. -   2. Heat Maps:     The platform visualizes a retailer's floor plan, shelf layouts, and     other store environments with overlays showing levels of various     kinds of activity. -   1. Examples:     -   1. Maps for places people walk past, but don't handle any of the         products.     -   2. Maps for where on the floor people stand when interacting         with products.     -   3. Misplaced Items:         The platform tracks all of a store's SKUs. When an item gets put         in the incorrect place, the platform will know where that item         is and build a log. At some threshold, or immediately, store         employees may be alerted to the misplaced item. Alternatively,         the staff may access the Misplaced Item Map in the Store App.         When convenient, staff can then quickly locate and correct         misplaced items.         7.1.2 Standard Assist     -   The Store App will display a store's floor plan.     -   It will display a graphic to represent each person in the store.     -   When the graphic is selected, via touch, click, or other means,         pertinent information to store employees will be displayed. For         example: Shopping Cart items (items they have collected) will         appear in a list.     -   If the platform has a confidence level below a predetermined         threshold for a particular item(s) and for a period of time that         is in a person's possession (Shopping Cart), their graphic         (currently a dot) will indicate the difference. The app uses a         color change. Green indicates high confidence and yellow/orange         indicates lower confidence.     -   Store employees with the Store App can be notified of the lower         confidence. They can go make sure the customer's Shopping Cart         is accurate.     -   Through the Store App, employees of the retailer adjust a         customer's Shopping Cart items (add or delete).

7.1.3 Standard LP

-   -   If a shopper is using the Shopper App, they simply exit the         store and are charged. However, if they are not, they will need         to use the Guest App to pay for the items in their Shopping         Cart.     -   If the shopper bypasses the Guest App on their way out of the         store, their graphic indicates they must be approached before         exiting. The App uses a change of color to red. Staff also         receive a notification of potential loss.     -   Through the Store App, employees of the retailer adjust a         customer's Shopping Cart items (add or delete).

7.2 Non-Store App

The following analytic features represent additional capabilities of the platform.

7.2.1 Standard Analytics

-   1. Product Interactions:     Granular breakdown of product interactions such as:     -   a. Interaction time to conversion ratios for each product.     -   b. AB comparisons (color, style, etc.). Some of the smaller         products on display have multiple options like colors, flavors,         etc.         -   Is the rose gold handled more than the silver?         -   Do blue cans attract more interactions than red ones? -   2. Directional Impressions:     Know the difference between a location based impression and where     the shopper's gaze is. If they are looking at a product that is 15     feet away, for 20 seconds, the impression should not count for where     they are, but for where they are looking. -   3. Customer Recognition:     Remember repeat shoppers and their associated email address     (collected in a variety of ways by the retailer) and shopping     profiles. -   4. Group Dynamics:     Decide when a shopper is watching someone else interact with a     product.     -   Answer whether that person interacts with the product         afterwards?     -   Did those people enter the store together, or are they likely         strangers?     -   Do individuals or groups of people spend more time in the store?         5. Customer Touchback:         Offer customers targeted information, post store experience.         This feature may have a slightly different implementation with         each retailer depending on particular practices and policies. It         may require integration and/or development from the retailer to         adopt the feature.     -   Shoppers would be asked if they wished to receive notifications         about products they might be interested in. That step may be         integrated with the store's method of collecting emails.     -   After leaving the store, a customer may receive an email with         the products they spent time with at the store. An interaction         threshold for duration, touch, and sight (direction impressions)         will be decided. When the threshold is met, the products would         make it to her list and be sent to her soon after leaving the         store.

Additionally, or alternatively, the shopper could be sent an email a period of time later that offered product(s) on sale or other special information. These products will be items they expressed interest in, but did not purchase.

7.3 Guest App

The Shopper App automatically checks people out when they exit the store. However, the platform does not require shoppers to have or use the Shopper App to use the store.

When a shopper/person does not have or use the Shopper App they walk up to a kiosk (an iPad/tablet or other screen) or they walk up to a pre-installed self-checkout machine. The display, integrated with the platform, will automatically display the customer's Shopping Cart.

The shopper will have the opportunity to review what is displayed. If they agree with the information on the display they can either enter cash into the machine (if that capability is built into the hardware (e.g. self-checkout machines)) or they swipe their credit or debit card. They can then exit the store.

If they disagree with the display, store staff is notified by their selection to challenge through a touch screen, button, or other means. (see the Store Assist under the Store App)

7.4 Shopper App

Through use of an app, the Shopper App, the customer can exit the store with merchandise and automatically be charged and given a digital receipt. The shopper must open their app at any time while within the store's shopping area. The platform will recognize a unique image that is displayed on the shopper's device. The platform will tie them to their account (Customer Association), and regardless if they keep the app open or not, will be able to remember who they are throughout their time in the store's shopping area.

As the shopper gathers items, the Shopper App will display the items in shopper's Shopping Cart. If the shopper wishes, they can view product information about each item they pick up (i.e. gets added to their shopping cart). Product information is stored either with the store's systems or added to a platform. The ability for updating that information, such as offering product sales or displaying prices, is an option the retailer can request/purchase or develop.

When a shopper puts an item down, it is removed from their Shopping Cart on the backend and on the Shopper App.

If the Shopper App is opened, and then closed after Customer Association is completed, the Platform will maintain the shopper's Shopping Cart and correctly charge them once they exit the store.

The Shopper App also has mapping information on its development roadmap. It can tell a customer where to find items in the store if the customer requests the information by typing in the item being sought. At a later date, we will take a shopper's shopping list (entered into the app manually or through other intelligent systems) and display the fastest route through the store to collect all the desired items. Other filters, such as ‘Bagging Preference’ may be added. The Bagging Preference filter allows a shopper to not follow the fastest route, but to gather sturdier items first, then more fragile items later.

8. Types of Customers

Member customer—First type of customer logs into the system using an app. The customer is prompted with a picture and when s/he clicks on it, the system links that to the internal id of that customer. If the customer has an account, then the account is charged automatically when the customer walks out of the store. This is the membership based store.

Guest customer—Not every store will have membership, or customers may not have a smartphone or a credit card. This type of customer will walk up to a kiosk. The kiosk will display the items that the customer has and will ask the customer to put in the money. The kiosk will already know about all the items that the customer has bought. For this type of customer, the system is able to identify if the customer has not paid for the items in the shopping cart, and prompt the checker at the door, before the customer reaches there, to let the checker know about unpaid items. The system can also prompt for one item that has not been paid for, or the system having low confidence about one item. This is referred to as predictive pathfinding.

The system assigns color codes (green and yellow) to the customers walking in the store based on the confidence level. The green color coded customers are either logged into the system or the system has a high confidence about them. Yellow color coded customers have one or more items that are not predicted with high confidence. A clerk can look at the yellow dots and click on them to identify problem items, walk up to the customer and fix the problem.

9. Analytics

A host of analytics information is gathered about the customer such as how much time a customer spent in front of a particular shelf. Additionally, the system tracks the location where a customer is looking (impression on the system), and the items which a customer picked and put back on the shelf. Such analytics are currently available in ecommerce but not available in retail stores.

10. Functional Modules

The following is a list of functional modules:

-   1. System capturing array of images in store using synchronized     cameras. -   2. System to identify joints in images, and sets of joints of     individual persons. -   3. System to create new persons using joint sets. -   4. System to delete ghost persons using joint sets. -   5. System to track individual persons over time by tracking joint     sets. -   6. System to generate region proposals for each person present in     the store indicating the SKU number of item in the hand (WhatCNN). -   7. System to perform get/put analysis for region proposals     indicating if the item in the hand was picked up or placed onto the     shelf (WhenCNN). -   8. System to generate inventory array per person using region     proposals and get/put analysis (Outputs of WhenCNN combined with     heuristics, stored joint locations of persons, and precomputed map     of items on the store shelves). -   9. System to identify, track and update locations of misplaced items     on shelves. -   10. System to track changes (get/put) to items on shelves using     pixel-based analysis. -   11. System to perform inventory audit of store. -   12. System to identify multiple items in hands. -   13. System to collect item image data from store using shopping     scripts. -   14. System to perform checkout and collect payment from member     customers. -   15. System to perform checkout and collect payment from guest     customers. -   16. System to perform loss-prevention by identifying un-paid items     in a cart. -   17. System to track customers using color codes to help clerks     identify incorrectly identified items in a customer's cart. -   18. System to generate customer shopping analytics including     location-based impressions, directional impressions, AB analysis,     customer recognition, group dynamics etc. -   19. System to generate targeted customer touchback using shopping     analytics. -   20. System to generate heat map overlays of the store to visualize     different activities.

The technology described herein can support Cashier-free Checkout. Go to Store. Take Things. Leave.

Cashier-free Checkout is a pure machine vision and deep learning based system. Shoppers skip the line and get what they want faster and easier. No RFID tags. No changes to store's backend systems. Can be integrated with 3^(rd) party Point of Sale and Inventory Management systems.

Real time 30 FPS analysis of every video feed.

On-premise, cutting edge GPU cluster.

Recognizes shoppers and the items they interact with.

No internet dependencies in example embodiment.

Multiple state-of-the-art deep learning models, including proprietary custom algorithms, to resolve gaps in machine vision technology for the first time.

Techniques & Capabilities include the following:

-   -   1. Standard Cognition's machine learning pipeline solves:         -   a) People Detection.         -   b) Entity Tracking.         -   c) Multicamera Person Agreement.         -   d) Hand Detection.         -   e) Item Classification.         -   f) Item Ownership Resolution.

Combining these techniques, we can:

-   1. Keep track of all people throughout their shopping experience in     real time. -   2. Know what shoppers have in their hand, where they stand, and what     items they place back. -   3. Know which direction shoppers are facing and for how long. -   4. Recognize misplaced items and perform 24/7 Visual Merchandizing     Audits.

Can detect exactly what a shopper has in their hand and in their basket.

Learning Your Store:

Custom neural networks trained on specific stores and items. Training data is reusable across all store locations.

Standard Deployment:

Ceiling cameras must be installed with double coverage of all areas of the store. Requires between 2 and 6 cameras for a typical aisle.

An on-premise GPU cluster can fit into one or two server racks in a back office.

Example systems can be integrated with or include Point of Sale and Inventory Management systems.

A first system, method and computer program product for capturing arrays of images in stores using synchronized cameras.

A second system, method and computer program product to identify joints in images, and sets of joints of individual persons.

A third system, method and computer program product to create new persons using joint sets.

A fourth system, method and computer program product to delete ghost persons using joint sets.

A fifth system, method and computer program product to track individual persons over time by tracking joint sets.

A sixth system, method and computer program product to generate region proposals for each person present in the store indicating the SKU number of an item in the hand (WhatCNN).

A seventh system, method and computer program product to perform get/put analysis for region proposals indicating if the item in the hand was picked up or placed onto the shelf (WhenCNN).

An eighth system, method and computer program product to generate an inventory array per person using region proposals and get/put analysis (e.g. Outputs of WhenCNN combined with heuristics, stored joint locations of persons, and precomputed map of items on the store shelves).

A ninth system, method and computer program product to identify, track and update locations of misplaced items on shelves.

A tenth system, method and computer program product to track changes (get/put) to items on shelves using pixel-based analysis.

An eleventh system, method and computer program product to perform inventory audits of a store.

A twelfth system, method and computer program product to identify multiple items in hands.

A thirteenth system, method and computer program product to collect item image data from a store using shopping scripts.

A fourteenth system, method and computer program product to perform checkout and collect payment from member customers.

A fifteenth system, method and computer program product to perform checkout and collect payment from guest customers.

A sixteenth system, method and computer program product to perform loss-prevention by identifying un-paid items in a cart.

A seventeenth system, method and computer program product to track customers using for example color codes to help clerks identify incorrectly identified items in a customer's cart.

An eighteenth system, method and computer program product to generate customer shopping analytics including one or more of location-based impressions, directional impressions, AB analysis, customer recognition, group dynamics etc.

A nineteenth system, method and computer program product to generate targeted customer touchback using shopping analytics.

A twentieth system, method and computer program product to generate heat map overlays of the store to visualize different activities.

A twenty first system, method and computer program for Hand Detection.

A twenty second system, method and computer program for Item Classification.

A twenty third system, method and computer program for Item Ownership Resolution.

A twenty fourth system, method and computer program for Item People Detection.

A twenty fifth system, method and computer program for Item Entity Tracking.

A twenty sixth method and computer program for Item Multicamera Person Agreement.

A twenty seventh system, method and computer program product for cashier-less checkout substantially as described herein.

Combinations of any of systems 1-26 with any other system or systems in systems 1-26 listed above.

Described herein is a method for tracking puts and takes of inventory items by subjects in an area of real space, comprising:

-   -   using a plurality of cameras to produce respective sequences of         images of corresponding fields of view in the real space, the         field of view of each camera overlapping with the field of view         of at least one other camera in the plurality of cameras;     -   receiving the sequences of images from the plurality of cameras,         and using first image recognition engines to process images to         generate first data sets that identify subjects and locations of         the identified subjects in the real space;

processing the first data sets to specify bounding boxes which include images of hands of identified subjects in images in the sequences of images;

-   -   receiving the sequences of images from the plurality of cameras,         and processing the specified bounding boxes in the images to         generate a classification of hands of the identified subjects         using second image recognition engines, the classification         including whether the identified subject is holding an inventory         item, a first nearness classification indicating a location of a         hand of the identified subject relative to a shelf, a second         nearness classification indicating a location of a hand of the         identified subject relative to a body of the identified subject,         a third nearness classification indicating a location of a hand         of the identified subject relative to a basket associated with         an identified subject, and an identifier of a likely inventory         item; and     -   processing the classifications of hands for sets of images in         the sequences of images of identified subjects to detect takes         of inventory items by identified subjects and puts of inventory         items on shelves by identified subjects.

In this described method the first data sets can comprise for each identified subject sets of candidate joints having coordinates in real space.

This described method can include processing the first data sets to specify bounding boxes includes specifying bounding boxes based on locations of joints in the sets of candidate joints for each subject.

In this described method one or both of the first and the second image recognition engines can comprise convolutional neural networks.

This described method can include processing the classifications of bounding boxes using convolutional neural networks.

A computer program product and products are described which include a computer readable memory comprising a non-transitory data storage medium, and computer instructions stored in the memory executable by a computer to track puts and takes of inventory items by subjects in an area of real space by any of the herein described processes.

A system is described comprising a plurality of cameras producing a sequences of images including a hand of a subject; and a processing system coupled to the plurality of cameras, the processing system including a hand image recognition engine, receiving the sequence of images, to generate classifications of the hand in time sequence, and logic to process the classifications of the hand from the sequence of images to identify an action by the subject, wherein, the action is one of puts and takes of inventory items.

The system can include logic to identify locations of joints of the subject in the images in the sequences of images, and to identify bounding boxes in corresponding images that include the hands of the subject based on the identified joints. 

What is claimed is:
 1. A system for tracking puts and takes of inventory items by subjects in an area of real space, comprising: a plurality of cameras, cameras in the plurality of cameras producing respective sequences of images of corresponding fields of view in the real space, the field of view of each camera overlapping with the field of view of at least one other camera in the plurality of cameras; a processing system coupled to the plurality of cameras, the processing system including a plurality of image recognition engines, receiving corresponding sequences of images from the plurality of cameras, image recognition engines in the plurality of image recognition engines processing the images in the corresponding sequences to identify subjects represented in the images; and logic to process sets of images in the sequences of images that include the identified subjects to detect takes of inventory items by identified subjects and puts of inventory items on shelves by identified subjects, wherein the logic to process sets of images includes: for identified subjects, logic to process images to generate classifications of the images of the identified subjects, the classifications including whether the identified subject is holding an inventory item, a first nearness classification indicating a location of a hand of the identified subject relative to a shelf, a second nearness classification indicating a location a hand of the identified subject relative to the identified subject.
 2. The system of claim 1, wherein the second nearness classification indicates a location of a hand of the identified subject relative to a body of the identified subject, and the generated classifications include a third nearness classification indicating a location of a hand of the identified subject relative to a basket associated with an identified subject.
 3. The system of claim 1, including logic to perform time sequence analysis over the classifications of images to detect said takes and said puts by the identified subjects.
 4. The system of claim 1, wherein the logic to process sets of images includes: for identified subjects, logic to identify bounding boxes of data representing hands in images in the sets of images of the identified subjects, and to process data in the bounding boxes to generate classifications of data within the bounding boxes for the identified subjects.
 5. The system of claim 3, wherein the classifications include whether the identified subject is holding an inventory item, a first nearness classification indicating a location of a hand of the identified subject relative to a shelf, a second nearness classification indicating a location a hand of the identified subject relative to a body of the identified subject, a third nearness classification indicating a location a hand of the identified subject relative to a basket associated with an identified subject, and an identifier of a likely inventory item.
 6. The system of claim 3, including logic to perform time sequence analysis over the classifications of data within the bounding boxes in the sets of images to detect said takes and said puts by the identified subjects.
 7. The system of claim 1, wherein the logic to process sets of images comprises convolutional neural networks.
 8. The system of claim 1, wherein cameras in the plurality of cameras are configured to generate synchronized sequences of images.
 9. The system of claim 1, wherein the plurality of cameras comprise cameras disposed over and having fields of view encompassing respective parts of the area in real space.
 10. The system of claim 1, including logic responsive to the detected takes and puts, to generate log data structures including a list of inventory items for identified subjects.
 11. A method for tracking puts and takes of inventory items by subjects in an area of real space, the method including: using a plurality of cameras to produce respective sequences of images of corresponding fields of view in the real space, the field of view of each camera overlapping with the field of view of at least one other camera in the plurality of cameras; receiving corresponding sequences of images from the plurality of cameras, processing the images in the corresponding sequences using image recognition engines in a plurality of image recognition engines and identifying subjects represented in the images wherein the plurality of image recognition engines are part of a processing system coupled to the plurality of cameras; and processing sets of images in the sequences of images that include the identified subjects to detect takes of inventory items by identified subjects and puts of inventory items on shelves by identified subjects, wherein the processing sets of images includes: for identified subjects, generating classifications of the images of the identified subjects, the classifications including whether the identified subject is holding an inventory item, a first nearness classification indicating a location of a hand of the identified subject relative to a shelf, a second nearness classification indicating a location of a hand of the identified subject relative to a body of the identified subject, a third nearness classification indicating a location a hand of the identified subject relative to a basket associated with an identified subject, and an identifier of a likely inventory item.
 12. The method of claim 11, including performing time sequence analysis over the classifications of images to detect said takes and said puts by the identified subjects.
 13. The method of claim 11, wherein the processing sets of images includes: for identified subjects, identifying bounding boxes of data representing hands in images in the sets of images of the identified subjects, and processing data in the bounding boxes to generate classifications of data within the bounding boxes for the identified subjects.
 14. The method of claim 13, including performing time sequence analysis over the classifications of data within the bounding boxes in the sets of images to detect said takes and said puts by the identified subjects.
 15. The method of claim 11, including circular buffers coupled to cameras in the plurality of cameras to store sets of images in the sequences of images from the plurality of cameras.
 16. The method of claim 11, including processing sets of images using convolutional neural networks.
 17. The method of claim 11, wherein cameras in the plurality of cameras are configured to generate synchronized sequences of images.
 18. The method of claim 11, wherein the plurality of cameras comprise cameras disposed over and having fields of view encompassing respective parts of the area in real space.
 19. The method of claim 11, including responsive to the detected takes and puts, generating a log data structure including a list of inventory items for each identified subject.
 20. A system for tracking puts and takes of inventory items by subjects in an area of real space, comprising: a plurality of cameras, cameras in the plurality of cameras producing respective sequences of images of corresponding fields of view in the real space, the field of view of each camera overlapping with the field of view of at least one other camera in the plurality of cameras; a processing system coupled to the plurality of cameras, the processing system including: first image recognition engines, receiving the sequences of images from the plurality of cameras, which process images to generate first data sets that identify subjects and locations of the identified subjects in the real space; logic to process the first data sets to specify bounding boxes which include images of hands of identified subjects in images in the sequences of images; second image recognition engines, receiving the sequences of images from the plurality of cameras, which process the specified bounding boxes in the images to generate a classification of hands of the identified subjects, the classification including whether the identified subject is holding an inventory item, a first nearness classification indicating a location of a hand of the identified subject relative to a shelf, a second nearness classification indicating a location of a hand of the identified subject relative to the identified subject, and an identifier of a likely inventory item; and logic to process the classifications of hands for sets of images in the sequences of images of identified subjects to detect takes of inventory items by identified subjects and puts of inventory items on shelves by identified subjects; and logic to generate a log data structure including a list of inventory items for each identified subject.
 21. The system of claim 20, including circular buffers coupled to cameras in the plurality of cameras to store sets of images in the sequences of images from the plurality of cameras for processing by corresponding ones of the first and second image recognition engines.
 22. The system of claim 20, wherein the first data sets comprise for each identified subject sets of candidate joints having coordinates in real space.
 23. The system of claim 20, wherein the logic to process the first data sets to specify bounding boxes specifies bounding boxes based on locations of joints in the sets of candidate joints for each subject.
 24. The system of claim 20, wherein the second image recognition engines comprise convolutional neural networks.
 25. The system of claim 20, wherein the logic to process the classifications of bounding boxes comprise convolutional neural networks.
 26. The system of claim 20, wherein cameras in the plurality of cameras are configured to generate synchronized sequences of images.
 27. The system of claim 20, wherein the plurality of cameras comprise cameras disposed over and having fields of view encompassing respective parts of the area in real space. 